Triple
T16096357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashyyyk |
E390493
|
entity |
| Predicate | cityArchitecture |
P87338
|
FINISHED |
| Object | elevated cities |
—
|
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: elevated cities | Statement: [Kashyyyk, cityArchitecture, elevated cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityArchitecture Context triple: [Kashyyyk, cityArchitecture, elevated cities]
-
A.
cityView
Indicates that one entity offers a view of, or overlooks, a city.
-
B.
urbanDesignElement
chosen
Indicates a relationship where something functions as a designed feature or component that shapes the form, use, or experience of an urban environment.
-
C.
architectOfSurroundingBuildings
Indicates that one entity is the architect responsible for designing the buildings that surround or are adjacent to another specified entity.
-
D.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
E.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.