Triple
T306563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Ironsides |
E6315
|
entity |
| Predicate | workAbout |
P380
|
FINISHED |
| Object | War of 1812 naval heroics of USS Constitution |
—
|
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: War of 1812 naval heroics of USS Constitution | Statement: [Old Ironsides, workAbout, War of 1812 naval heroics of USS Constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAbout Context triple: [Old Ironsides, workAbout, War of 1812 naval heroics of USS Constitution]
-
A.
workBecame
Indicates that one work was transformed, adapted, or evolved into another work over time.
-
B.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
C.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
D.
isAbout
chosen
Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by another entity.
-
E.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea313be88190b4441f3ea41a99e2 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.