Triple
T27515369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold Hickory |
E694536
|
entity |
| Predicate | provesTo |
P163271
|
FINISHED |
| Object | his community |
—
|
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: his community | Statement: [Harold Hickory, provesTo, his community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provesTo Context triple: [Harold Hickory, provesTo, his community]
-
A.
provesTo
chosen
Indicates that one entity demonstrates or establishes the truth or validity of something to another entity.
-
B.
proved
Indicates that one entity has demonstrated the truth or validity of another entity (such as a statement, theorem, or claim) through logical or evidential means.
-
C.
provedInFullBy
Indicates that something (such as a claim, theorem, or statement) has been completely and rigorously demonstrated or established by a particular agent or source.
-
D.
independentlyProvedBy
Indicates that a statement or result is established by a proof that does not rely on or derive from another specified proof or source.
-
E.
partiallyProvenFor
Indicates that something has been shown to hold or be true for part of a domain or set of cases, but not yet for all cases.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 1:18 p.m.