Triple
T9118015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | From the Conquest to 1930 panel |
E218771
|
entity |
| Predicate | endTimeDepicted |
P80890
|
FINISHED |
| Object | circa 1930 |
—
|
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: circa 1930 | Statement: [From the Conquest to 1930 panel, endTimeDepicted, circa 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeDepicted Context triple: [From the Conquest to 1930 panel, endTimeDepicted, circa 1930]
-
A.
tookPlaceUntil
chosen
Indicates that an event or situation occurred continuously or repeatedly up to a specified end time or date, after which it no longer took place.
-
B.
timeOfAppearance
Indicates the specific time at which an entity or event becomes visible, present, or first occurs.
-
C.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
D.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
E.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a5e2ac8190b602ef0c77deb2fa |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.