Triple
T25642565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convoy |
E642871
|
entity |
| Predicate | hasCarrierType |
P160278
|
FINISHED |
| Object | owner-operators |
—
|
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: owner-operators | Statement: [Convoy, hasCarrierType, owner-operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarrierType Context triple: [Convoy, hasCarrierType, owner-operators]
-
A.
carrierType
chosen
Indicates the type or category of carrier involved in the relationship or action (e.g., the kind of entity that carries or transports something).
-
B.
requiresCarrierSupport
Indicates that performing or enabling this action depends on support or approval from a carrier (e.g., a mobile network operator).
-
C.
hasCellularComponent
Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
-
D.
basedOnCarrierType
Indicates that something is determined or defined according to the type or category of carrier involved.
-
E.
carrierOf
Indicates that one entity serves as the medium, vehicle, or host that contains, transports, or conveys 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 5:45 p.m.