Triple
T10534540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Structure II |
E248528
|
entity |
| Predicate | likelyPrimaryUse |
P75472
|
FINISHED |
| Object | royal residential and administrative complex |
—
|
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 residential and administrative complex | Statement: [Structure II, likelyPrimaryUse, royal residential and administrative complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyPrimaryUse Context triple: [Structure II, likelyPrimaryUse, royal residential and administrative complex]
-
A.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
-
B.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
C.
primarilyUsedBy
Indicates that something is mainly or most commonly used by a particular entity or group.
-
D.
laterPrimarilyUsedFor
Indicates that something was initially used for one purpose but, at a later time, came to be used mainly for another specified purpose.
-
E.
originalPrimaryUse
chosen
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a1a754c8190b53f2df28a1dfef1 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:31 p.m.