Triple
T1108860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaping Lena |
E25546
|
entity |
| Predicate | refersToEra |
P4343
|
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: [Leaping Lena, refersToEra, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToEra Context triple: [Leaping Lena, refersToEra, early 20th century]
-
A.
positionInEra
Indicates the temporal placement or role of something within a specific historical or chronological era.
-
B.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
C.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
-
D.
refersToPeriod
chosen
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
E.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e6134481909f348986a25f65c6 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b749e2a881909ef28745a7d2d917 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.