Triple
T1412816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African wild dog |
E31841
|
entity |
| Predicate | digitNumber |
P11851
|
FINISHED |
| Object | four toes on each foot |
—
|
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: four toes on each foot | Statement: [African wild dog, digitNumber, four toes on each foot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitNumber Context triple: [African wild dog, digitNumber, four toes on each foot]
-
A.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
B.
hasDigitCount
chosen
Indicates that one entity has a total number of digits equal to the value specified by the other entity.
-
C.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
D.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
E.
notableNumber
Indicates that a number associated with an entity is distinguished or significant in some notable way (e.g., record-setting, symbolic, or otherwise remarkable).
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e3383c81909acb9c6c1c3b817a |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.