Triple
T37613111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin Guggenheim |
E935839
|
entity |
| Predicate | embarkedOnTitanicAt |
P105227
|
FINISHED |
| Object | Cherbourg, France |
—
|
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: Cherbourg, France | Statement: [Benjamin Guggenheim, embarkedOnTitanicAt, Cherbourg, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embarkedOnTitanicAt Context triple: [Benjamin Guggenheim, embarkedOnTitanicAt, Cherbourg, France]
-
A.
typicalEmbarkedForce
Indicates the usual or characteristic military force that is boarded onto a vehicle, vessel, or transport platform for an operation or mission.
-
B.
shipBoardedFrom
chosen
Indicates that an entity boarded a ship originating from or at a specified location or source.
-
C.
arrivedAtTitanicSite
Indicates that an entity has reached the location of the Titanic wreck site.
-
D.
shipSurvived
Indicates that a ship remained intact and continued to exist or operate after a potentially destructive event or period.
-
E.
setAboard
Indicates placing or causing someone or something to be on or into a vehicle, vessel, or other mode of transport.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.