Triple
T28809577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Carla |
E727472
|
entity |
| Predicate | inUniverseRegionType |
P99968
|
FINISHED |
| Object | coastal city |
—
|
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: coastal city | Statement: [Santa Carla, inUniverseRegionType, coastal city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseRegionType Context triple: [Santa Carla, inUniverseRegionType, coastal city]
-
A.
inUniverseRegion
chosen
Indicates that an entity is located within or belongs to a specific universe-defined region or area.
-
B.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
C.
inUniverseLocationType
Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
-
D.
inUniverseRestriction
Indicates that something is limited, applicable, or valid only within a specific fictional or defined universe or continuity.
-
E.
inUniverseNetworkType
Indicates that one entity has a specific type or category of network within a particular fictional or defined universe in relation to 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 6:30 a.m.