Triple
T4748816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President's Match |
E105426
|
entity |
| Predicate | usesTargets |
P57765
|
FINISHED |
| Object | bullseye rifle targets |
—
|
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: bullseye rifle targets | Statement: [President's Match, usesTargets, bullseye rifle targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTargets Context triple: [President's Match, usesTargets, bullseye rifle targets]
-
A.
usesTarget
chosen
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
B.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
C.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
D.
usesTargetingSystem
Indicates that an entity employs or relies on a specific targeting system to aim at or select a target.
-
E.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64c6f5ac81908a62f9c17e77ac86 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.