Triple
T24607426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Ant system |
E609012
|
entity |
| Predicate | hasBroad |
P156722
|
FINISHED |
| Object | Barton Broad |
—
|
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: Barton Broad | Statement: [River Ant system, hasBroad, Barton Broad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroad Context triple: [River Ant system, hasBroad, Barton Broad]
-
A.
isBroad
Indicates that something has a large width or extensive scope relative to a reference or context.
-
B.
isBroadBased
Indicates that something has a wide scope or foundation, encompassing many elements, aspects, or participants rather than being narrow or limited.
-
C.
hasBroadRegion
Indicates that an entity is associated with, located in, or applicable to a relatively large or general geographic or conceptual region.
-
D.
hasReach
Indicates that one entity is able to extend its influence, access, or physical span to another entity or area.
-
E.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
- F. None of above. chosen
Provenance (4 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:31 a.m.