Triple
T25951071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massive |
E653966
|
entity |
| Predicate | reasonForAliasUse |
P92674
|
FINISHED |
| Object | avoid reference to the Gulf War |
—
|
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: avoid reference to the Gulf War | Statement: [Massive, reasonForAliasUse, avoid reference to the Gulf War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForAliasUse Context triple: [Massive, reasonForAliasUse, avoid reference to the Gulf War]
-
A.
reasonForAlias
chosen
Indicates the justification or underlying cause for which an entity uses or is assigned a particular alias.
-
B.
usesAliasFor
Indicates that one entity employs an alternative name or identifier to refer to another entity.
-
C.
usedByAlias
Indicates that something is utilized, referenced, or accessed through an alternative name or alias.
-
D.
usesAliasTo
Indicates that one entity employs an alternative name or identifier to refer to or represent another entity.
-
E.
usesAliasWith
Indicates that one entity employs or operates under an alternative name or identifier in association 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 22, 2026, 8:44 a.m.