Triple
T27744035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isaac Hull |
E701928
|
entity |
| Predicate | shipNicknameAssociated |
P110548
|
FINISHED |
| Object | Old Ironsides |
—
|
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: Old Ironsides | Statement: [Isaac Hull, shipNicknameAssociated, Old Ironsides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipNicknameAssociated Context triple: [Isaac Hull, shipNicknameAssociated, Old Ironsides]
-
A.
shipNameWith
Indicates that a ship is associated with or identified by a particular name.
-
B.
shipAssociatedWith
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
-
C.
shipName
Indicates the name assigned to a specific ship in the relationship.
-
D.
namedVesselOf
chosen
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
-
E.
shipRegistry
Indicates that an entity is officially recorded or listed in a particular ship registry or registration system.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637189a3c8190865058cf6caaadc9 |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:14 p.m.