Triple
T24108638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | morung (youth dormitory) |
E597297
|
entity |
| Predicate | typicallyBuiltAt |
P155093
|
FINISHED |
| Object | central area of the village |
—
|
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: central area of the village | Statement: [morung (youth dormitory), typicallyBuiltAt, central area of the village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyBuiltAt Context triple: [morung (youth dormitory), typicallyBuiltAt, central area of the village]
-
A.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
B.
assembledAt
Indicates that one entity was put together or constructed at a specific location or facility.
-
C.
originallyBuilt
Indicates that one entity was the first or initial builder or constructor of another entity.
-
D.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
E.
factoryBuilt
Indicates that one entity constructed or established a factory for or at the location of another entity.
- F. None of above. chosen
Provenance (4 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de19057c819096a8b3290d33e2f6 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 11:02 p.m.