Triple
T1432280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States merchant marine |
E30474
|
entity |
| Predicate | roleInWartime |
P19322
|
FINISHED |
| Object | naval auxiliary |
—
|
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: naval auxiliary | Statement: [United States merchant marine, roleInWartime, naval auxiliary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWartime Context triple: [United States merchant marine, roleInWartime, naval auxiliary]
-
A.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
-
B.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
C.
statusDuringWar
chosen
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
D.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
E.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.