Triple
T22330083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States civil aircraft registry |
E552000
|
entity |
| Predicate | identifierPrefix |
P7142
|
FINISHED |
| Object | N |
—
|
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: N | Statement: [United States civil aircraft registry, identifierPrefix, N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifierPrefix Context triple: [United States civil aircraft registry, identifierPrefix, N]
-
A.
registrationPrefix
chosen
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
B.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
-
C.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
namespacePrefix
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
-
E.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
- F. None of above.
Provenance (3 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577a9c348190b8662142afa832be |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.