Triple
T637526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ovis |
E16657
|
entity |
| Predicate | includesDomesticForm |
P12776
|
FINISHED |
| Object | Ovis aries |
—
|
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: Ovis aries | Statement: [Ovis, includesDomesticForm, Ovis aries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDomesticForm Context triple: [Ovis, includesDomesticForm, Ovis aries]
-
A.
requiresDomesticLegislation
Indicates that the fulfillment, implementation, or enforcement of one entity depends on the adoption or existence of specific domestic legislation by another entity (typically a state or jurisdiction).
-
B.
containsForm
chosen
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
C.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
D.
includesStateOrProvince
Indicates that one entity geographically contains or encompasses a specific state or province within its boundaries.
-
E.
typicalCountryIncluded
Indicates that a country is commonly or characteristically included within a given grouping, context, or set.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a17b125481909a6ab53424954792 |
completed | March 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69a49d0629308190bcc137639567f7c2 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.