Triple
T36365625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saanen goat |
E895614
|
entity |
| Predicate | commonManagement |
P32595
|
FINISHED |
| Object | stall-fed with controlled rations |
—
|
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: stall-fed with controlled rations | Statement: [Saanen goat, commonManagement, stall-fed with controlled rations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonManagement Context triple: [Saanen goat, commonManagement, stall-fed with controlled rations]
-
A.
commonGroup
Indicates that the related entities belong to or participate in at least one group in common.
-
B.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
C.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
D.
collectiveAdministration
Indicates a relationship where multiple entities jointly manage, govern, or oversee a shared resource, process, or organization through shared decision-making authority.
-
E.
commonFor
chosen
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 3, 2026, 4:10 p.m.