Triple
T29062653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferae |
E735580
|
entity |
| Predicate | includesCommon |
P200080
|
FINISHED |
| Object | carnivorans |
—
|
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: carnivorans | Statement: [Ferae, includesCommon, carnivorans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCommon Context triple: [Ferae, includesCommon, carnivorans]
-
A.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
B.
includesCommonGroups
Indicates that two entities share at least one group or category in common.
-
C.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
D.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
-
E.
commonInclusionsName
Indicates that two or more entities share the same or very similar inclusion name, reflecting a common designation for included components or parts.
- F. None of above. chosen
Provenance (4 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
| PDg | Predicate description generation | batch_69ff70ebec7481908d8a4124c8d531df |
completed | May 9, 2026, 5:37 p.m. |
Created at: April 28, 2026, 10:16 a.m.