Triple
T38252569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nelson-class battleship |
E1014090
|
entity |
| Predicate | laidDownAfter |
P190207
|
FINISHED |
| Object | World War I |
—
|
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: World War I | Statement: [Nelson-class battleship, laidDownAfter, World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laidDownAfter Context triple: [Nelson-class battleship, laidDownAfter, World War I]
-
A.
laidDown
Indicates that an entity places or sets another entity down into a resting or horizontal position.
-
B.
laidDownBy
Indicates that something was established, created, or set as a rule, principle, or foundation by a particular agent.
-
C.
laidDownAs
Indicates that one entity has been formally established, stipulated, or prescribed as a rule, principle, or condition for another.
-
D.
laidDownDate
Indicates the date on which something (such as a rule, law, standard, or foundation) was formally established, set, or put in place.
-
E.
firstLaidDown
Indicates that one entity was the earliest to establish, formulate, or introduce another entity (such as a rule, idea, or structure).
- F. None of above. chosen
Provenance (4 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc330b4288190858b49d986160706 |
completed | May 7, 2026, 4:52 p.m. |
Created at: May 3, 2026, 4:30 p.m.