Triple
T25791663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wheeler Compromise in Louisiana |
E649562
|
entity |
| Predicate | hasBroker |
P162120
|
FINISHED |
| Object | William A. Wheeler |
E357776
|
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: William A. Wheeler | Statement: [Wheeler Compromise in Louisiana, hasBroker, William A. Wheeler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroker Context triple: [Wheeler Compromise in Louisiana, hasBroker, William A. Wheeler]
-
A.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
-
B.
hasAgent
Indicates that an action or event is carried out or initiated by a particular agent.
-
C.
hasRegistrar
Indicates that an entity is formally recorded or overseen by a specific registrar organization or authority.
-
D.
hasBroad
Indicates that one entity possesses or exhibits a wide or extensive scope, range, or coverage in relation to another entity or context.
-
E.
hasCollector
Indicates that an entity is associated with, or owned/curated by, a specific collector.
- F. None of above. chosen
Provenance (5 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a7d2750ae148190b6892053188ae827 |
completed | Aug. 13, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 22, 2026, 6 a.m.