Triple
T31400132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Samuel Browne |
E800973
|
entity |
| Predicate | VCActionDate |
P6878
|
FINISHED |
| Object | 1858-08-31 |
—
|
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: 1858-08-31 | Statement: [Sir Samuel Browne, VCActionDate, 1858-08-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VCActionDate Context triple: [Sir Samuel Browne, VCActionDate, 1858-08-31]
-
A.
visionDate
Indicates the date on which a particular vision, plan, or conceptual idea was created, recorded, or formally established.
-
B.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
automationDate
Indicates the date on which an action, process, or system becomes automated or is scheduled to be handled automatically.
-
D.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
E.
entryDate
Indicates the date on which an entity was first recorded, created, or entered into a system or context.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:19 p.m.