Triple
T643582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clinton's Ditch |
E16792
|
entity |
| Predicate | hasBroaderTerm |
P2372
|
FINISHED |
| Object | nicknames of public works |
—
|
LITERAL 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: nicknames of public works | Statement: [Clinton's Ditch, hasBroaderTerm, nicknames of public works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroaderTerm Context triple: [Clinton's Ditch, hasBroaderTerm, nicknames of public works]
-
A.
parentTaxon
Indicates that one taxonomic group is the immediate higher-level (parent) taxon of another taxonomic group.
-
B.
generalizationOf
chosen
Indicates that one entity represents a broader, more general concept or category that subsumes or abstracts over another, more specific entity.
-
C.
isBackboneOf
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
-
D.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
E.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f18216081908331aa12dac40214 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0a0ab481909871461418a00be7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.