Triple
T27090674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KACL |
E686157
|
entity |
| Predicate | basedInUniverseCity |
P180490
|
FINISHED |
| Object | Seattle |
—
|
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: Seattle | Statement: [KACL, basedInUniverseCity, Seattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInUniverseCity Context triple: [KACL, basedInUniverseCity, Seattle]
-
A.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
B.
homeTownInUniverse
Indicates that a location is the character’s hometown within a specified fictional or defined universe.
-
C.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
D.
cityOfFictionalOrigin
Indicates the city from which a fictional character, entity, or work is described as originating within its narrative or fictional universe.
-
E.
cityOfFictionalResidence
Indicates that a fictional character or entity resides in, or is associated with living in, a particular city within a narrative or fictional context.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 27, 2026, 8:40 a.m.