Triple
T14218820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Officer Jimmy |
E352430
|
entity |
| Predicate | hasOnScreenRoleType |
P87539
|
FINISHED |
| Object | supporting military officer |
—
|
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: supporting military officer | Statement: [Officer Jimmy, hasOnScreenRoleType, supporting military officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnScreenRoleType Context triple: [Officer Jimmy, hasOnScreenRoleType, supporting military officer]
-
A.
hasOnscreenFunction
chosen
Indicates that an entity serves a particular role or performs a specific function when it appears on screen.
-
B.
hasScreenType
Indicates the specific kind or category of screen associated with or used by an entity.
-
C.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
-
D.
hasScreenAppearanceType
Indicates the type or manner in which an entity appears or is presented on a screen.
-
E.
hasImageRole
Indicates that an image is associated with an entity in a specific functional or contextual role (e.g., thumbnail, icon, illustration).
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de621258d4819085f358cd2cf109e4 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:06 a.m.