Triple
T37651703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limatambo District |
E937190
|
entity |
| Predicate | hasAgriculturalTerraces |
P172319
|
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: [Limatambo District, hasAgriculturalTerraces, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgriculturalTerraces Context triple: [Limatambo District, hasAgriculturalTerraces, true]
-
A.
hasStandingTerraces
chosen
Indicates that an entity possesses or includes terraces that are fixed, elevated, and not retractable or temporary.
-
B.
usedTerracing
Indicates that an entity employed terracing techniques, such as creating stepped or leveled surfaces, in carrying out an activity or modifying land.
-
C.
hasTerracedWalls
Indicates that an entity possesses walls that are constructed in stepped or terraced levels rather than as a single continuous vertical surface.
-
D.
numberOfTerraces
Indicates the total count of terraces associated with a given entity.
-
E.
hasTerracesFromPeriod
Indicates that an entity possesses terraces that were constructed or are associated with a specific historical or chronological period.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.