Triple
T10343644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverside, Iowa |
E243686
|
entity |
| Predicate | selfProclaimed |
P18566
|
FINISHED |
| Object | future birthplace of Captain James T. Kirk |
—
|
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: future birthplace of Captain James T. Kirk | Statement: [Riverside, Iowa, selfProclaimed, future birthplace of Captain James T. Kirk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfProclaimed Context triple: [Riverside, Iowa, selfProclaimed, future birthplace of Captain James T. Kirk]
-
A.
coProclaimed
Indicates that two or more entities jointly made or issued the same formal declaration or announcement.
-
B.
selfIdentification
Indicates that an entity defines or declares its own identity, attributes, or classification about itself.
-
C.
considersItself
chosen
Indicates that an entity regards or perceives itself in a particular way, role, or state.
-
D.
reproclaimed
Indicates that something was proclaimed or announced again, typically reaffirming or restating a previous declaration.
-
E.
selfGoverning
Indicates that an entity has the authority and capacity to govern, regulate, and manage itself independently, without external control.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e92105888190a08104deb9d0cf1c |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:55 a.m.