Triple
T26167122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Belleau Wood (CVL-24) |
E654284
|
entity |
| Predicate | serviceInForeignNavyAs |
P157023
|
FINISHED |
| Object | Bois Belleau (R97) |
—
|
NE NERFINISHED |
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: Bois Belleau (R97) | Statement: [USS Belleau Wood (CVL-24), serviceInForeignNavyAs, Bois Belleau (R97)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceInForeignNavyAs Context triple: [USS Belleau Wood (CVL-24), serviceInForeignNavyAs, Bois Belleau (R97)]
-
A.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
-
B.
countryOfMilitaryService
Indicates that an entity served or is serving in the armed forces of a specified country.
-
C.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
D.
navalAffiliation
chosen
Indicates a formal relationship in which an entity is associated with, belongs to, or operates under a particular navy or naval force.
-
E.
captainServedUnder
Indicates that one captain performed their service or held their position under the authority or command of another person.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 26, 2026, 8:33 p.m.