Triple
T18385150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio Theater (Mesa Arts Center) |
E446563
|
entity |
| Predicate | isWithinComplexType |
P36917
|
FINISHED |
| Object | multi-venue arts center |
—
|
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: multi-venue arts center | Statement: [Studio Theater (Mesa Arts Center), isWithinComplexType, multi-venue arts center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinComplexType Context triple: [Studio Theater (Mesa Arts Center), isWithinComplexType, multi-venue arts center]
-
A.
positionWithinComplex
chosen
Indicates that one entity is located inside or forms a component part of a larger complex or compound structure.
-
B.
partOfComplexType
Indicates that an entity functions as a component or member within a larger, composite structure or complex type.
-
C.
containsCompoundType
Indicates that one entity includes or is composed of another entity of a specified compound type.
-
D.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
E.
isComposite
Indicates that an entity is made up of multiple components or parts combined into a single whole.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179ecde88190b0d88c519d49e995 |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.