Triple
T13734040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jelmore |
E329887
|
entity |
| Predicate | hasFictionalInfrastructure |
P15645
|
FINISHED |
| Object | roads |
—
|
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: roads | Statement: [Jelmore, hasFictionalInfrastructure, roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalInfrastructure Context triple: [Jelmore, hasFictionalInfrastructure, roads]
-
A.
hasFictionalEstablishmentType
Indicates that an establishment is associated with a particular type or category of fictional setting or institution.
-
B.
hasFictionalLocation
Indicates that an entity is associated with, set in, or takes place within a location that exists only in fiction rather than in the real world.
-
C.
hasFictionalInhabitants
Indicates that a place or setting is inhabited by fictional or imaginary beings.
-
D.
hasFictionalUniverseElement
chosen
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
E.
hasBranchInFictionalLocation
Indicates that an organization maintains a branch, office, or presence within a fictional or imaginary location.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0201d3c48190aa306be231a28bc1 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.