Triple
T18392920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thiesi |
E449781
|
entity |
| Predicate | hasTraditionalPastoralism |
P51842
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Thiesi, hasTraditionalPastoralism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalPastoralism Context triple: [Thiesi, hasTraditionalPastoralism, true]
-
A.
hasPastoralStructure
Indicates that an entity possesses or is organized according to a pastoral (shepherding or ministerial) governance or structural arrangement.
-
B.
historicallyNomadic
chosen
Indicates that an entity has traditionally led a mobile, wandering lifestyle without permanent settlement over a significant historical period.
-
C.
hasPastoralCenter
Indicates that an entity possesses or is associated with a pastoral center as one of its facilities or organizational components.
-
D.
hasTraditionalAnimalBreed
Indicates that an entity is associated with or possesses an animal that belongs to a recognized traditional breed.
-
E.
usesPastoralSetting
Indicates that the action or work is set in an idealized rural or countryside environment characteristic of pastoral themes.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e51844c1ec81909ec215db9b29612d |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.