Triple
T7362586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | traditional village of Wae Rebo |
E169785
|
entity |
| Predicate | centralSpace |
P19218
|
FINISHED |
| Object | ceremonial courtyard |
—
|
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: ceremonial courtyard | Statement: [traditional village of Wae Rebo, centralSpace, ceremonial courtyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralSpace Context triple: [traditional village of Wae Rebo, centralSpace, ceremonial courtyard]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
C.
hasCentralSpace
chosen
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
-
D.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
E.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:06 p.m.