Triple
T913435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estates-General of 1789 |
E19715
|
entity |
| Predicate | timeSincePreviousSession |
P21475
|
FINISHED |
| Object | 175 years |
—
|
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: 175 years | Statement: [Estates-General of 1789, timeSincePreviousSession, 175 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSincePreviousSession Context triple: [Estates-General of 1789, timeSincePreviousSession, 175 years]
-
A.
lastSession
Indicates that one session is the final or most recent session associated with a given entity or sequence of sessions.
-
B.
sessionLength
Indicates the duration of time that a particular session lasts from start to end.
-
C.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
D.
lastSessionDate
Indicates the date on which the most recent session involving the entity took place.
-
E.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2f605bc8190a5245aa2ca55cf43 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b2918ea881908698020b995a8eae |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b2f4e3fc81908c8a2d1fbef9c5d2 |
completed | March 1, 2026, 9:43 p.m. |
Created at: March 1, 2026, 7:39 p.m.