Triple
T29785303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Battle of Fort Fisher |
E756244
|
entity |
| Predicate | powderBoatPlanAdvocate |
P168182
|
FINISHED |
| Object | Benjamin F. Butler |
—
|
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: Benjamin F. Butler | Statement: [First Battle of Fort Fisher, powderBoatPlanAdvocate, Benjamin F. Butler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powderBoatPlanAdvocate Context triple: [First Battle of Fort Fisher, powderBoatPlanAdvocate, Benjamin F. Butler]
-
A.
boatStudio
Indicates a relationship where a boat is associated with, produced by, or represented by a particular studio or production company.
-
B.
boatPower
Indicates a relationship where a boat is characterized by or associated with a specific power rating or propulsion strength.
-
C.
sailPlan
Indicates a plan or arrangement for how a vessel will be sailed, including intended route, timing, and sailing configuration.
-
D.
sixthBoat
Indicates that an entity is the sixth boat in an ordered sequence or arrangement of boats.
-
E.
landingCraft
Indicates a vehicle or vessel specifically used to transport and set down people or cargo from one location onto a surface, typically from water or air to land.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674a9cc8481909068fcdcc8ed7dab |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 5:08 p.m.