Triple
T19532294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Palo Alto |
E488684
|
entity |
| Predicate | sawCombatService |
P38978
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [SS Palo Alto, sawCombatService, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawCombatService Context triple: [SS Palo Alto, sawCombatService, no]
-
A.
sawCombat
chosen
Indicates that an entity directly participated in active military or armed conflict.
-
B.
sawCombatant
Indicates that one entity directly observed or witnessed another entity who is engaged as a combatant in a conflict or battle.
-
C.
sawServiceIn
Indicates that an entity observed or experienced a particular service within a specified context, location, or timeframe.
-
D.
sawServiceDuring
Indicates that one entity experienced or utilized a service during the time period associated with another entity or event.
-
E.
combatServiceIdentification
Indicates that an entity is assigned a specific identifier used to distinguish and recognize it during combat operations or military engagements.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363fd1f8819080805346efad2579 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.