Triple
T12130100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wunmonije compound |
E288910
|
entity |
| Predicate | inferredFunction |
P14773
|
FINISHED |
| Object | royal or elite residential compound |
—
|
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: royal or elite residential compound | Statement: [Wunmonije compound, inferredFunction, royal or elite residential compound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inferredFunction Context triple: [Wunmonije compound, inferredFunction, royal or elite residential compound]
-
A.
inferredType
Indicates that an entity has a type or category that has been deduced or derived rather than explicitly stated.
-
B.
possibleFunction
chosen
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
C.
usedToInfer
Indicates that one entity serves as a basis or source from which another entity is logically derived or concluded.
-
D.
associatedFunction
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
E.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91841615c819097f20a7447a1b8f4 |
completed | April 10, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69d91508f8008190b3a90ec0bf0953ca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.