Triple
T13295322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRT Dark Red Line |
E316664
|
entity |
| Predicate | hasInfrastructureOwnerType |
P109389
|
FINISHED |
| Object | public authority |
—
|
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 authority | Statement: [MRT Dark Red Line, hasInfrastructureOwnerType, public authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfrastructureOwnerType Context triple: [MRT Dark Red Line, hasInfrastructureOwnerType, public authority]
-
A.
hasInfrastructureOwner
Indicates that one entity owns or is responsible for the infrastructure associated with another entity.
-
B.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
C.
ownerOfInfrastructureUsed
Indicates that one entity owns the infrastructure that is being used by another entity or activity.
-
D.
hasCapitalOwnerRole
Indicates that an entity holds the role or status of owning capital in relation to another entity or asset.
-
E.
ownedInfrastructureClass
Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:28 p.m.