Triple
T17541832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACAN |
E427216
|
entity |
| Predicate | isInstalledOn |
P3054
|
FINISHED |
| Object | aircraft carriers |
—
|
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: aircraft carriers | Statement: [TACAN, isInstalledOn, aircraft carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInstalledOn Context triple: [TACAN, isInstalledOn, aircraft carriers]
-
A.
installedAt
chosen
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
B.
preinstalledOn
Indicates that a software or component comes already installed and ready to use on a particular device or system before the user receives it.
-
C.
installedInstrument
Indicates that one entity has placed or set up another entity as an instrument or device for use in a particular context or system.
-
D.
installedBy
Indicates that one entity was set up, put in place, or made operational through the actions or intervention of another entity.
-
E.
installedPower
Indicates the total nominal power capacity that has been set up or equipped for use in a system, device, or facility.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4545e64448190a2a63bc13f549027 |
completed | April 19, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.