Triple
T36769859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Congress |
E908444
|
entity |
| Predicate | hasMeetingEndDate |
P118268
|
FINISHED |
| Object | November 1899 |
—
|
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: November 1899 | Statement: [Revolutionary Congress, hasMeetingEndDate, November 1899]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeetingEndDate Context triple: [Revolutionary Congress, hasMeetingEndDate, November 1899]
-
A.
hasMeetingStartDate
Indicates the date and time at which a scheduled meeting is set to begin.
-
B.
hasCollectionEndDate
Indicates the date on which a collection activity, period, or process is scheduled or recorded to end.
-
C.
hasWorkPeriodEnd
Indicates the point in time at which a specified work period or shift concludes.
-
D.
hasTemporalEnd
chosen
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
E.
hasMeeting
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or place.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: May 3, 2026, 4:12 p.m.