Triple
T26698378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Navy Ensign |
E673086
|
entity |
| Predicate | flownFrom |
P161131
|
FINISHED |
| Object | stern of commissioned Philippine Navy ships |
—
|
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: stern of commissioned Philippine Navy ships | Statement: [Philippine Navy Ensign, flownFrom, stern of commissioned Philippine Navy ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flownFrom Context triple: [Philippine Navy Ensign, flownFrom, stern of commissioned Philippine Navy ships]
-
A.
flownAt
Indicates that an entity has traveled or been transported by air at a specified time, place, or condition.
-
B.
flownWhen
Indicates that one entity has been flown or transported at a specific time or under certain temporal conditions associated with another entity.
-
C.
flownWith
Indicates that two entities have traveled together on the same flight or aircraft.
-
D.
flownOver
Indicates that one entity has moved through the air above or across another entity or location.
-
E.
flownToIndicate
Indicates that one entity has traveled by air to reach or visit another entity or location.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6177d33d88190a4f33193a0551c08 |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 3:30 a.m.