Triple
T24383609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1898 U.S. Naval Court of Inquiry |
E614679
|
entity |
| Predicate | objectHasRole |
P133192
|
FINISHED |
| Object | USS Maine (subject of investigation) |
—
|
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 Maine (subject of investigation) | Statement: [1898 U.S. Naval Court of Inquiry, objectHasRole, USS Maine (subject of investigation)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectHasRole Context triple: [1898 U.S. Naval Court of Inquiry, objectHasRole, USS Maine (subject of investigation)]
-
A.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
requiresRole
Indicates that performing an action or accessing a resource is contingent on the subject having a specified role or set of roles.
-
C.
includesRoles
Indicates that one entity contains or encompasses one or more specified roles within its scope or structure.
-
D.
roleOnVoyager
Indicates the specific position, duty, or function an entity holds in relation to the Voyager mission or project.
-
E.
roleWith
chosen
Indicates that one entity holds or performs a particular role in relation to another entity.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294533b3881908c228a021c254006 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.