Triple
T20822918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyūga-class helicopter destroyer |
E512621
|
entity |
| Predicate | commandFacilities |
P88406
|
FINISHED |
| Object | enhanced C4I systems |
—
|
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: enhanced C4I systems | Statement: [Hyūga-class helicopter destroyer, commandFacilities, enhanced C4I systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandFacilities Context triple: [Hyūga-class helicopter destroyer, commandFacilities, enhanced C4I systems]
-
A.
userFacility
Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
-
B.
hasCommandFacilities
chosen
Indicates that an entity possesses locations, infrastructure, or resources used for command, control, or leadership functions.
-
C.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
-
D.
findingOnFacilities
Indicates a relationship where an inspection or assessment identifies a specific issue, observation, or result associated with particular facilities.
-
E.
campusFacility
Indicates that one entity is a facility that is located on or belongs to a particular campus.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2fb49148190bdad1b51e7dac43a |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.