Triple
T4500914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of August First |
E101215
|
entity |
| Predicate | namedForDate |
P13719
|
FINISHED |
| Object | 1 August 1927 |
—
|
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: 1 August 1927 | Statement: [Order of August First, namedForDate, 1 August 1927]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForDate Context triple: [Order of August First, namedForDate, 1 August 1927]
-
A.
namedDuring
Indicates that an entity received its name during a specified time period or event.
-
B.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
designatedDayFor
chosen
Indicates that a specific day is officially assigned or reserved for a particular purpose, event, or activity.
-
D.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
E.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56f9dca08190b926f40e201a3e97 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.