Triple
T29172610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCTC |
E739511
|
entity |
| Predicate | projectTypeManaged |
P166384
|
FINISHED |
| Object | roadway improvements |
—
|
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: roadway improvements | Statement: [RCTC, projectTypeManaged, roadway improvements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectTypeManaged Context triple: [RCTC, projectTypeManaged, roadway improvements]
-
A.
productTypeManaged
Indicates that an entity is responsible for overseeing, controlling, or administering a particular type of product.
-
B.
classificationTypeManaged
Indicates that the classification type is controlled or administered through a managed process or system rather than being assigned freely or ad hoc.
-
C.
branchManaged
Indicates that one entity is responsible for managing or overseeing the operations of a particular branch of an organization.
-
D.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
E.
programManaged
Indicates that one entity is responsible for overseeing, organizing, or administering a program associated with another entity.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6633dd454819081c59443e6d3197c |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 11:53 a.m.