Triple
T22362071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDOT |
E552801
|
entity |
| Predicate | systemManaged |
P147908
|
FINISHED |
| Object | highway system of Mississippi |
—
|
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: highway system of Mississippi | Statement: [MDOT, systemManaged, highway system of Mississippi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemManaged Context triple: [MDOT, systemManaged, highway system of Mississippi]
-
A.
operatingSystemManaged
Indicates that the entity is controlled, configured, or handled automatically by the operating system rather than by user-level or application-level mechanisms.
-
B.
registryManaged
Indicates that an entity is controlled, maintained, or overseen by a central registry or registration authority.
-
C.
environmentManagedBy
Indicates that the control, maintenance, or oversight of an environment is carried out by a specified managing entity.
-
D.
modeManaged
Indicates that one entity controls, configures, or oversees the operational mode or state of another entity.
-
E.
isManagedThrough
Indicates that one entity is administered, controlled, or operated by means of another entity, typically specifying the mechanism, channel, or system used for its management.
- F. None of above. chosen
Provenance (4 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d44a908190b16e4cfdf4591b10 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.