Triple
T7534276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viverridae |
E178107
|
entity |
| Predicate | includesCommonGroups |
P77673
|
FINISHED |
| Object | civets |
—
|
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: civets | Statement: [Viverridae, includesCommonGroups, civets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCommonGroups Context triple: [Viverridae, includesCommonGroups, civets]
-
A.
hasCommonAncestryGroup
Indicates that the related entities share membership in the same ancestral or lineage-based group.
-
B.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
C.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
D.
hasCommunityOverlap
Indicates that two entities share a portion of the same community, membership base, or audience.
-
E.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84a9d28819084ebfc44fcb2c29c |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5cea2748190afd607ef93e8d66c |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:47 p.m.