Triple
T4164161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NP44 |
E84400
|
entity |
| Predicate | hasCodePrefix |
P49384
|
FINISHED |
| Object | NP |
—
|
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: NP | Statement: [NP44, hasCodePrefix, NP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodePrefix Context triple: [NP44, hasCodePrefix, NP]
-
A.
hasCodeContext
Indicates that an entity is associated with or occurs within a particular programming or code-related context.
-
B.
tailCodePrefix
Indicates that one entity’s tail code begins with, or is prefixed by, the string represented by the other entity.
-
C.
hasCodeName
Indicates that an entity is known or referred to by a particular alternative name or alias, often used for secrecy or distinction.
-
D.
hasCodeLetters
Indicates that an entity is associated with, or represented by, a specific sequence of letters used as its code or identifier.
-
E.
hasAirportCodePrefix
chosen
Indicates that an airport’s code begins with a specified sequence of characters.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.