Triple
T23062446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO (as supported asset) |
E574939
|
entity |
| Predicate | usesInformationFor |
P150823
|
FINISHED |
| Object | target tracking |
—
|
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: target tracking | Statement: [NATO (as supported asset), usesInformationFor, target tracking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInformationFor Context triple: [NATO (as supported asset), usesInformationFor, target tracking]
-
A.
usesInformationSources
Indicates that an entity relies on or consults specified information sources to perform actions, make decisions, or obtain knowledge.
-
B.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
C.
usedInforms
Indicates that one entity utilizes information from another entity to guide or shape its own actions, decisions, or outputs.
-
D.
usesDataIn
Indicates that one entity relies on, accesses, or incorporates data from another entity in performing its function or operation.
-
E.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
- F. None of above. chosen
Provenance (4 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a0c3c881909f137ad511c216ac |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:55 p.m.