Triple
T34128424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | d’Eyquem |
E875356
|
entity |
| Predicate | denotesLineageOrOrigin |
P3325
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [d’Eyquem, denotesLineageOrOrigin, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesLineageOrOrigin Context triple: [d’Eyquem, denotesLineageOrOrigin, yes]
-
A.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
B.
basedOnCharacterLineage
Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
-
C.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
E.
proposedAsAncestralOriginOf
Indicates that something is suggested or hypothesized to be the ancestral source or origin of something else.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.