Triple
T7532621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etihad Cargo |
E178062
|
entity |
| Predicate | operatesOnRoutes |
P70721
|
FINISHED |
| Object | global network |
—
|
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: global network | Statement: [Etihad Cargo, operatesOnRoutes, global network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnRoutes Context triple: [Etihad Cargo, operatesOnRoutes, global network]
-
A.
operatedOnRoute
Indicates that a transportation service or vehicle was active and provided service along a specified route.
-
B.
operatedRoutes
chosen
Indicates that an agent (such as a company or organization) runs or manages specific routes, typically providing services along those paths.
-
C.
operatesOnLayer
Indicates that an entity performs actions or functions specifically targeting a particular layer within a layered structure or system.
-
D.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
E.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84753fc81908bee2013004ef5fb |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.