Triple
T27623349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle between USS Constitution and HMS Guerriere |
E696136
|
entity |
| Predicate | nicknameOriginOf |
P64332
|
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: [Battle between USS Constitution and HMS Guerriere, nicknameOriginOf, Old Ironsides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOriginOf Context triple: [Battle between USS Constitution and HMS Guerriere, nicknameOriginOf, Old Ironsides]
-
A.
nameOriginExplanation
Indicates that an explanation is provided for the origin or derivation of a given name.
-
B.
nameEtymologyFor
chosen
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
C.
characterNameOrigin
Indicates the source or inspiration from which a character’s name is derived.
-
D.
unitNamesakeOf
Indicates that a particular unit (such as an organization, division, or group) is named in honor of, or derives its name from, a specific entity.
-
E.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:16 p.m.