Triple
T8287233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Region and Language |
E193812
|
entity |
| Predicate | hasSettingCategory |
P13407
|
FINISHED |
| Object | Formats |
—
|
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: Formats | Statement: [Region and Language, hasSettingCategory, Formats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettingCategory Context triple: [Region and Language, hasSettingCategory, Formats]
-
A.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
B.
hasCategoryGroup
chosen
Indicates that something is associated with, or belongs to, a broader grouping of related categories.
-
C.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
-
D.
hasSettingRole
Indicates that an entity participates in a setting by fulfilling a specific contextual or functional role within it.
-
E.
hasNotableSettingBy
Indicates that the subject has a notable or significant setting that was created, designed, or established by the specified 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad4b2008190ad1624e1335147c6 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.