Triple
T173208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Society |
E3520
|
entity |
| Predicate | distributorRegion |
P285
|
FINISHED |
| Object | theatrical |
—
|
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: theatrical | Statement: [High Society, distributorRegion, theatrical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributorRegion Context triple: [High Society, distributorRegion, theatrical]
-
A.
distributor
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
-
B.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
C.
beneficiaryRegion
Indicates the region that receives the benefit, advantage, or positive impact resulting from an action, resource, or arrangement.
-
D.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
sourceRegion
Indicates the geographic or spatial region from which something originates or is derived.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e1ec008190a89dd452f72574f4 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a256689f908190afeb5ee82022a911 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.