Triple
T10020781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedouin communities |
E200603
|
entity |
| Predicate | contemporaryTrend |
P39078
|
FINISHED |
| Object | partial sedentarization |
—
|
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: partial sedentarization | Statement: [Bedouin communities, contemporaryTrend, partial sedentarization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryTrend Context triple: [Bedouin communities, contemporaryTrend, partial sedentarization]
-
A.
contemporary
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
B.
designTrend
Indicates a prevailing or emerging stylistic direction or pattern that influences how something is designed over a period of time.
-
C.
trendy
Indicates that something is currently fashionable, popular, or in line with prevailing styles or tastes.
-
D.
trends
chosen
Indicates that one entity exhibits a general direction of change or development over time in relation to another reference or context.
-
E.
contemporaryUse
Indicates that something is currently used or practiced in the present time or modern 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd777b208190ad75eac79eec0c2f |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.