Triple
T20002138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise Saunders |
E494357
|
entity |
| Predicate | lifespanOverlapWith |
P95490
|
FINISHED |
| Object | 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: 20th century | Statement: [Louise Saunders, lifespanOverlapWith, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifespanOverlapWith Context triple: [Louise Saunders, lifespanOverlapWith, 20th century]
-
A.
sharedLifePeriodWith
chosen
Indicates that two entities existed or were alive during at least one overlapping period of time.
-
B.
overlapsWith
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
C.
livesBetween
Indicates that one entity resides at a location that is spatially situated between two other reference entities or locations.
-
D.
hasJurisdictionOverlapWith
Indicates that two authorities or entities share some portion of legal or regulatory control over the same area, subject, or set of activities.
-
E.
geographicOverlap
Indicates that two geographic areas share at least part of the same physical space or territory.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a2e34481908a495cc5d077c41f |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.