Triple
T10471909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cofiroute |
E246941
|
entity |
| Predicate | operatesUnderRegime |
P12605
|
FINISHED |
| Object | public concession contracts |
—
|
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: public concession contracts | Statement: [Cofiroute, operatesUnderRegime, public concession contracts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesUnderRegime Context triple: [Cofiroute, operatesUnderRegime, public concession contracts]
-
A.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
-
B.
governedByLegalRegime
chosen
Indicates that an entity is subject to, regulated by, or operating under a specific legal framework or set of legal rules.
-
C.
operatesUnderControlOf
Indicates that one entity functions or carries out its activities subject to the authority, direction, or governance of another entity.
-
D.
regimeName
Indicates that a particular name or label is assigned to a specific regime.
-
E.
regimeDescription
Indicates that an entity provides a textual characterization or explanation of a particular regime, system, or governing arrangement.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5094cec788190a485c5c9e7cd024a |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:20 p.m.