Triple
T1201589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USED |
E25792
|
entity |
| Predicate | usesAcronymStyle |
P4130
|
FINISHED |
| Object | all-caps letter acronym |
—
|
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: all-caps letter acronym | Statement: [USED, usesAcronymStyle, all-caps letter acronym]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAcronymStyle Context triple: [USED, usesAcronymStyle, all-caps letter acronym]
-
A.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
-
B.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
C.
usedWithStyle
chosen
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
-
D.
establishesAbbreviation
Indicates that one entity defines or introduces an abbreviated form that stands for another entity.
-
E.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with another 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9fece4819089a6a2d61e61fa2e |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.