Triple
T30944161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile Bay Ferry |
E788342
|
entity |
| Predicate | terminalAt |
P85899
|
FINISHED |
| Object | Fort Morgan, Alabama |
—
|
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: Fort Morgan, Alabama | Statement: [Mobile Bay Ferry, terminalAt, Fort Morgan, Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalAt Context triple: [Mobile Bay Ferry, terminalAt, Fort Morgan, Alabama]
-
A.
terminalArea
Indicates that one entity is a designated terminal area or zone associated with another entity (such as a facility, system, or region).
-
B.
terminalLocation
chosen
Indicates the specific terminal or endpoint location associated with an entity or process.
-
C.
terminalName
Indicates the name or label assigned to a specific terminal or endpoint within a system or network.
-
D.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
-
E.
TerminalEUsedFor
Indicates that a terminal E is used for a particular purpose, function, or activity.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 8:53 p.m.