Triple
T38434263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Shahran |
E903891
|
entity |
| Predicate | hasLifestyleHistory |
P138411
|
FINISHED |
| Object | pastoralism |
—
|
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: pastoralism | Statement: [Al Shahran, hasLifestyleHistory, pastoralism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLifestyleHistory Context triple: [Al Shahran, hasLifestyleHistory, pastoralism]
-
A.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
B.
hasPriorHistory
chosen
Indicates that an entity has a previously recorded occurrence, condition, or involvement relevant to the current context.
-
C.
hasSubhistory
Indicates that one history or sequence of events is a component, segment, or nested part of another, larger history.
-
D.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
E.
hasResearchHistory
Indicates that an entity has a documented record of past research activities, projects, or studies.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:31 p.m.