Triple
T24722292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fédération Aéronautique Internationale |
E612338
|
entity |
| Predicate | usesRecordCode |
P157690
|
FINISHED |
| Object | FAI sporting code |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: FAI sporting code | Statement: [Fédération Aéronautique Internationale, usesRecordCode, FAI sporting code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRecordCode Context triple: [Fédération Aéronautique Internationale, usesRecordCode, FAI sporting code]
-
A.
trackRecordUsedFor
Indicates that a track record is utilized as a basis or input for some subsequent decision, evaluation, or process.
-
B.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
-
C.
usesLineCode
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
-
D.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
-
E.
isRecord
Indicates that one entity functions as an official or authoritative record of another entity or of some information.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 3:41 a.m.