Triple
T29742722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canis mosbachensis |
E752656
|
entity |
| Predicate | isAncestorOrCloseRelativeOf |
P151648
|
FINISHED |
| Object | Canis lupus |
—
|
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: Canis lupus | Statement: [Canis mosbachensis, isAncestorOrCloseRelativeOf, Canis lupus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAncestorOrCloseRelativeOf Context triple: [Canis mosbachensis, isAncestorOrCloseRelativeOf, Canis lupus]
-
A.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
-
B.
siblingOrRelative
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
C.
isGrandchildOf
Indicates that one person is the grandchild (child of a child) of another person.
-
D.
hasAncestralTo
chosen
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
E.
isNephewOf
Indicates that one person is the male child of another person's sibling.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673645c888190bdffeb6448487ec4 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:49 p.m.