Triple
T31686136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity Land |
E808665
|
entity |
| Predicate | firstChartedInPeriod |
P88712
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Trinity Land, firstChartedInPeriod, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstChartedInPeriod Context triple: [Trinity Land, firstChartedInPeriod, early 19th century]
-
A.
firstChartEntryDate
Indicates the date on which an entity first appeared or was recorded on a particular chart or ranking.
-
B.
recordedInPeriodStart
chosen
Indicates that an event or record began or was first documented at the start of a specified time period.
-
C.
acquiredInPeriod
Indicates that one entity was acquired by another within a specified time period.
-
D.
firstPerformedDuring
Indicates that an action, event, or performance occurred for the first time within a specified time period or during a particular event.
-
E.
representedPeriodStart
Indicates the starting point in time of the period that the subject is intended to represent.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:06 p.m.