Triple
T9171645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Roebling |
E220093
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Karl Roebling |
E220093
|
NE 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: Karl Roebling | Statement: [Karl Roebling, name, Karl Roebling]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karl Roebling Context triple: [Karl Roebling, name, Karl Roebling]
-
A.
Karl Roebling
chosen
Karl Roebling was a founder and early settler associated with the establishment of Saxonburg, Pennsylvania.
-
B.
Karl Roebling
Karl Roebling was a member of the prominent Roebling family associated with American civil engineering and bridge construction.
-
C.
Edmund Roebling
Edmund Roebling is a member of the Roebling family, historically known for its prominent role in American civil engineering and bridge construction.
-
D.
Charles Roebling
Charles Roebling was an American civil engineer and industrialist best known for helping complete the Brooklyn Bridge and leading the John A. Roebling's Sons wire rope company.
-
E.
Ferdinand Roebling
Ferdinand Roebling was a member of the prominent Roebling family associated with major 19th-century American engineering and industrial enterprises.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae38ee48190bf783477bc37913d |
completed | April 1, 2026, 5:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05c077f008190ba1bcd82b3fe9a1d |
completed | April 4, 2026, 12:32 a.m. |
Created at: March 30, 2026, 7:22 p.m.