Triple
T5158257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrick Joseph Hayes |
E116366
|
entity |
| Predicate | startTimeAsCardinal |
P62290
|
FINISHED |
| Object | 1924-03-24 |
—
|
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: 1924-03-24 | Statement: [Patrick Joseph Hayes, startTimeAsCardinal, 1924-03-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsCardinal Context triple: [Patrick Joseph Hayes, startTimeAsCardinal, 1924-03-24]
-
A.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
B.
startTimeAsCaesar
Indicates the time at which an event or action begins, expressed in the Caesar (Julian) calendar time standard.
-
C.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
D.
startTimeAsCCPBase
Indicates that the referenced time value serves as the initial or baseline start time for an event or process within the CCP (Control/Command/Configuration) context.
-
E.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79bf9b088190a556dc02f10204e4 |
completed | March 20, 2026, 4:45 p.m. |
Created at: March 20, 2026, 1:44 p.m.