Triple
T12024544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Scion Group |
E286240
|
entity |
| Predicate | operatesPropertyType |
P47037
|
FINISHED |
| Object | purpose-built student accommodation |
—
|
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: purpose-built student accommodation | Statement: [The Scion Group, operatesPropertyType, purpose-built student accommodation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesPropertyType Context triple: [The Scion Group, operatesPropertyType, purpose-built student accommodation]
-
A.
operatesUnitType
chosen
Indicates that an entity runs, manages, or controls a unit of a specified type.
-
B.
venueTypeOperated
Indicates that an entity operates or manages a venue of a specified type.
-
C.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
-
D.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
E.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.