Triple
T9817121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGill, Nevada |
E238435
|
entity |
| Predicate | layoutTypeHistoric |
P66217
|
FINISHED |
| Object | planned company town |
—
|
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: planned company town | Statement: [McGill, Nevada, layoutTypeHistoric, planned company town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutTypeHistoric Context triple: [McGill, Nevada, layoutTypeHistoric, planned company town]
-
A.
historicalType
chosen
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
B.
historicalMapAppearance
Indicates that an entity is depicted or referenced on a particular historical map at a given time or period.
-
C.
historicalLayer
Indicates a relationship where one entity represents or belongs to a particular historical stratum, phase, or period relative to another.
-
D.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
E.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f4a1548190a5afc5ee0d7da392 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:30 p.m.