Triple
T10739327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LX |
E253278
|
entity |
| Predicate | canAppearAs |
P76230
|
FINISHED |
| Object | operating carrier 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: operating carrier code | Statement: [LX, canAppearAs, operating carrier code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAppearAs Context triple: [LX, canAppearAs, operating carrier code]
-
A.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
B.
mayAppear
chosen
Indicates that an entity is allowed or has the possibility to be present or occur in association with another entity or context.
-
C.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
-
D.
mayAppearOn
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
-
E.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710424d8c81908ee9b59d622f2af5 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.