Triple
T18100444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tzofar/Al-Ghamr area |
E433199
|
entity |
| Predicate | landUseRegime |
P63885
|
FINISHED |
| Object | special land-use arrangements |
—
|
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: special land-use arrangements | Statement: [Tzofar/Al-Ghamr area, landUseRegime, special land-use arrangements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landUseRegime Context triple: [Tzofar/Al-Ghamr area, landUseRegime, special land-use arrangements]
-
A.
landUseContext
Indicates the contextual setting or circumstances under which a particular piece of land is used or designated for a specific purpose.
-
B.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
C.
territorialUse
chosen
Indicates the use, control, or occupation of a geographic area or territory by an entity.
-
D.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
E.
otherLandUse
Indicates that the land is used for purposes that do not fall into any of the primary or predefined land-use categories.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb5e6208190b3c3cce3b95d66ad |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.