Triple
T5912808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reading Railroad |
E131502
|
entity |
| Predicate | MonopolyColorGroup |
P50270
|
FINISHED |
| Object | railroads |
—
|
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: railroads | Statement: [Reading Railroad, MonopolyColorGroup, railroads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MonopolyColorGroup Context triple: [Reading Railroad, MonopolyColorGroup, railroads]
-
A.
MonopolyBoardColorGroup
chosen
Indicates that multiple Monopoly properties belong to the same color-coded property group on the game board.
-
B.
monopolyGrantedBy
Indicates that one party has been given exclusive control or rights over a market, resource, or activity by another authority or entity.
-
C.
monopolyOn
Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
-
D.
monopolyRestricted
Indicates that an entity’s monopoly power or exclusive control over a market, resource, or service is limited, regulated, or otherwise constrained.
-
E.
isMonopoly
Indicates that one entity exclusively controls a market or resource, facing no significant competition.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.