Triple
T17119638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branch Davidians |
E415430
|
entity |
| Predicate | confrontationStartDate |
P22233
|
FINISHED |
| Object | 1993-02-28 |
—
|
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: 1993-02-28 | Statement: [Branch Davidians, confrontationStartDate, 1993-02-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confrontationStartDate Context triple: [Branch Davidians, confrontationStartDate, 1993-02-28]
-
A.
conflictStartTime
chosen
Indicates the specific point in time at which a conflict between entities begins.
-
B.
contestedAt
Indicates that an event, claim, or outcome is being challenged or disputed at a particular time or place.
-
C.
escalationDate
Indicates the date on which an issue, case, or situation was formally escalated to a higher level of attention or authority.
-
D.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
E.
dateOfFirstMeeting
Indicates the specific date on which two or more entities first met or came together.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e8092b548190b45c1695be47edc2 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.