Triple
T15079691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waunakee |
E380103
|
entity |
| Predicate | claimToUniqueness |
P22891
|
FINISHED |
| Object | only community named Waunakee in the world |
—
|
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: only community named Waunakee in the world | Statement: [Waunakee, claimToUniqueness, only community named Waunakee in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimToUniqueness Context triple: [Waunakee, claimToUniqueness, only community named Waunakee in the world]
-
A.
uniqueClaim
chosen
Indicates that a claim is distinct and not duplicated or shared with any other claim in the given context.
-
B.
claim1
Indicates that an entity asserts, alleges, or maintains the truth of a particular statement, proposition, or fact.
-
C.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
D.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
E.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff80008c88190840f94222f867478 |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:03 a.m.