Triple
T15985730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AA shoulder sleeve insignia |
E387686
|
entity |
| Predicate | usedSinceConflict |
P2935
|
FINISHED |
| Object | World War I era |
—
|
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: World War I era | Statement: [AA shoulder sleeve insignia, usedSinceConflict, World War I era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSinceConflict Context triple: [AA shoulder sleeve insignia, usedSinceConflict, World War I era]
-
A.
usedSince
chosen
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
B.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
C.
existedDuringConflict
Indicates that an entity was present or active for some or all of the duration of a specified conflict.
-
D.
controlledSince
Indicates that one entity has held control or authority over another entity starting from a specified point in time.
-
E.
conflictUse
Indicates a relationship where one entity’s use, application, or operation is incompatible with, obstructs, or negatively interferes with another entity’s use.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.