Triple
T33534405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G. I. Gurdjieff |
E858879
|
entity |
| Predicate | birthDateNote |
P79593
|
FINISHED |
| Object | Exact birth year uncertain; various sources give 1866, 1872, or 1877 |
—
|
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: Exact birth year uncertain; various sources give 1866, 1872, or 1877 | Statement: [G. I. Gurdjieff, birthDateNote, Exact birth year uncertain; various sources give 1866, 1872, or 1877]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthDateNote Context triple: [G. I. Gurdjieff, birthDateNote, Exact birth year uncertain; various sources give 1866, 1872, or 1877]
-
A.
subjectBirthDate
Indicates the date on which the subject was born.
-
B.
dateOfBirth
Indicates the specific calendar date on which an individual or entity was born.
-
C.
childBirthDate
Indicates the date on which a child was born in relation to a parent or parental entity.
-
D.
uncertainBirthDate
chosen
Indicates that the exact birth date of an entity is not known or is only approximately specified.
-
E.
namedAfterDateOfBirth
Indicates that something (such as a person, event, or entity) is named after a specific date corresponding to a birth.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.