Triple
T26259649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS New Haven (CL-76) |
E656811
|
entity |
| Predicate | reorderedAs |
P4692
|
FINISHED |
| Object | USS Belleau Wood (CVL-24) |
—
|
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: USS Belleau Wood (CVL-24) | Statement: [USS New Haven (CL-76), reorderedAs, USS Belleau Wood (CVL-24)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reorderedAs Context triple: [USS New Haven (CL-76), reorderedAs, USS Belleau Wood (CVL-24)]
-
A.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
B.
joinedOrderOf
Indicates that an entity became a member of, or formally joined, a particular order or organization.
-
C.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
D.
reorganizedFor
Indicates that one entity has been rearranged, restructured, or otherwise modified in its organization for the benefit, use, or requirements of another entity.
-
E.
orderedBy
chosen
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dfdd57c81908d069fc4b8124ff7 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:09 p.m.