Triple
T3942882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower of Silence |
E92075
|
entity |
| Predicate | statusInSomeRegions |
P33417
|
FINISHED |
| Object | restricted use |
—
|
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: restricted use | Statement: [Tower of Silence, statusInSomeRegions, restricted use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInSomeRegions Context triple: [Tower of Silence, statusInSomeRegions, restricted use]
-
A.
statusInRegion
chosen
Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
-
B.
regionStatus
Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
-
C.
internationalAvailability
Indicates that something is available or accessible across multiple countries or regions beyond a single national boundary.
-
D.
availableInCountry
Indicates that something can be legally or practically obtained, accessed, or used within a specified country.
-
E.
supportsRegionRestriction
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.