Triple
T38645035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsair |
E938692
|
entity |
| Predicate | abilityTargets |
P143292
|
FINISHED |
| Object | ground units and buildings |
—
|
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: ground units and buildings | Statement: [Corsair, abilityTargets, ground units and buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abilityTargets Context triple: [Corsair, abilityTargets, ground units and buildings]
-
A.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
B.
canTarget
chosen
Indicates that one entity is able or permitted to select, aim at, or direct its action or effect toward another entity as a target.
-
C.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
D.
availabilityTarget
Indicates that something is the intended object, resource, or condition whose availability is being specified, monitored, or constrained.
-
E.
targetsProvidedBy
Indicates that one entity supplies or makes available specific targets for another entity to use or act upon.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.