Triple
T36837311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo le Gris |
E910307
|
entity |
| Predicate | hasFamilyNameOfRealPerson |
P52579
|
FINISHED |
| Object | de Greiff |
—
|
NE NERFINISHED |
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: de Greiff | Statement: [Leo le Gris, hasFamilyNameOfRealPerson, de Greiff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyNameOfRealPerson Context triple: [Leo le Gris, hasFamilyNameOfRealPerson, de Greiff]
-
A.
hasGivenNameOfRealPerson
Indicates that an entity bears the same given (first) name as a specific real person.
-
B.
hasNamesakeFamilyName
Indicates that two entities share the same family name, with one serving as the namesake for the other's family name.
-
C.
hasFamilyNameOf
chosen
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
D.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
E.
hasAncestralFamilyName
Indicates that an entity bears or is associated with a family name inherited from its ancestors.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:13 p.m.