Triple
T29143449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Whateley |
E738700
|
entity |
| Predicate | livesInTimePeriod |
P3869
|
FINISHED |
| Object | early 20th 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 20th century | Statement: [Old Whateley, livesInTimePeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesInTimePeriod Context triple: [Old Whateley, livesInTimePeriod, early 20th century]
-
A.
appearsInTimePeriod
Indicates that an entity is present, active, or occurs within a specified time period.
-
B.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
C.
livedDuring
chosen
Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
-
D.
livesBetween
Indicates that one entity resides at a location that is spatially situated between two other reference entities or locations.
-
E.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662707bfc819093d188364a088311 |
completed | May 2, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:38 a.m.