Triple
T5135062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Shepherd |
E115798
|
entity |
| Predicate | primaryFunctionHistorically |
P2417
|
FINISHED |
| Object | farm dog |
—
|
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: farm dog | Statement: [Dutch Shepherd, primaryFunctionHistorically, farm dog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFunctionHistorically Context triple: [Dutch Shepherd, primaryFunctionHistorically, farm dog]
-
A.
primaryFunctionInPrehistory
Indicates the main role or use an entity had during prehistoric times, before written records.
-
B.
historicallyUsedFor
chosen
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
C.
primaryHistoricalSpecialism
Indicates that one entity’s main area of expertise or focus is a particular historical field or period.
-
D.
historicalFunction
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
E.
historicalCharacteristic
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
- 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_69bd44459a988190a772a5c2ec6a1965 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.