Triple
T18102739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowring |
E433267
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Bowring |
—
|
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: Bowring | Statement: [Bowring, name, Bowring]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bowring Context triple: [Bowring, name, Bowring]
-
A.
Bowring
chosen
Bowring was a notable British philhellene and political figure known for his support of Greek independence and his broader advocacy of liberal causes in the 19th century.
-
B.
Bongabong
Bongabong is a coastal agricultural municipality in the province of Oriental Mindoro in the Philippines, known for farming and fishing.
-
C.
Vingboons
Vingboons is the surname of a notable Dutch family of the 17th century that included prominent architects and cartographers such as Philips Vingboons.
-
D.
Akpabuyo
Akpabuyo is a coastal local government area in southeastern Nigeria known for its location near Calabar in Cross River State.
-
E.
Ozinga
Ozinga is a Dutch surname most notably associated with individuals such as Sjoukje Ozinga.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb7be948190b4ed4586f731d6f2 |
completed | April 19, 2026, 1:50 p.m. |
Created at: April 10, 2026, 10:28 a.m.