Triple
T24701807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Roses |
E611766
|
entity |
| Predicate | refersToLocationType |
P15985
|
FINISHED |
| Object | town |
—
|
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: town | Statement: [City of Roses, refersToLocationType, town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToLocationType Context triple: [City of Roses, refersToLocationType, town]
-
A.
refersToLocation
chosen
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
B.
subjectLocationType
Indicates the type or category of location associated with the subject in the relationship.
-
C.
currentLocationType
Indicates the type or category of place where an entity is currently located.
-
D.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
-
E.
supportsLocation
Indicates that one entity provides the necessary structure, foundation, or capacity to hold, host, or accommodate another entity at a particular place or position.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:23 a.m.