Triple
T31977933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasiliki |
E816496
|
entity |
| Predicate | hasBuildingOrganization |
P182776
|
FINISHED |
| Object | clustered room complexes |
—
|
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: clustered room complexes | Statement: [Vasiliki, hasBuildingOrganization, clustered room complexes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingOrganization Context triple: [Vasiliki, hasBuildingOrganization, clustered room complexes]
-
A.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
B.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
C.
hasOrganizations
Indicates that an entity is associated with, linked to, or includes one or more organizations.
-
D.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
E.
hasOrganizationFor
Indicates that one entity possesses, is associated with, or is responsible for a particular organization in relation to some context or purpose.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: May 1, 2026, 12:11 a.m.