Triple
T3186496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Savannah River Area |
E66709
|
entity |
| Predicate | hasCommonAcronymUsage |
P46512
|
FINISHED |
| Object | local media |
—
|
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: local media | Statement: [Central Savannah River Area, hasCommonAcronymUsage, local media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonAcronymUsage Context triple: [Central Savannah River Area, hasCommonAcronymUsage, local media]
-
A.
isCommonAbbreviation
Indicates that one term is a widely used shortened or abbreviated form of another term.
-
B.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
-
C.
hasAcronymExpansionLanguage
Indicates that a specified language is the language in which an acronym’s full expansion is expressed.
-
D.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
E.
hasCommonLoanwordsFrom
Indicates that two languages share loanwords that originate from the same source language.
- F. None of above. chosen
Provenance (4 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6c32ce88190a231be18d38ec5ba |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:06 p.m.