Triple
T21628910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panama Limited |
E533774
|
entity |
| Predicate | primaryClassOfService |
P81223
|
FINISHED |
| Object | first class |
—
|
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: first class | Statement: [Panama Limited, primaryClassOfService, first class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryClassOfService Context triple: [Panama Limited, primaryClassOfService, first class]
-
A.
primaryClass
chosen
Indicates that one entity is the main or principal classification category to which another entity belongs.
-
B.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
C.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
D.
primaryVariantInService
Indicates that a particular variant is the main or default version currently active or in use within a given service or system.
-
E.
primaryCode
Indicates that the referenced code is the main or most authoritative code associated with an entity, as opposed to any secondary or alternative codes.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5214e72c8190af109089f58fca4f |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.