Triple
T30473753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istanbul (Not Constantinople) |
E775382
|
entity |
| Predicate | referencesPlace |
P118404
|
FINISHED |
| Object | Constantinople |
—
|
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: Constantinople | Statement: [Istanbul (Not Constantinople), referencesPlace, Constantinople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referencesPlace Context triple: [Istanbul (Not Constantinople), referencesPlace, Constantinople]
-
A.
relatedPlace
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
B.
placeMentioned
chosen
Indicates that a specific place is referenced or mentioned in relation to another entity or context.
-
C.
foundationPlace
Indicates the place where an organization, institution, or similar entity was originally founded or established.
-
D.
referenceSectionFor
Indicates a relationship where one resource serves as the reference section or reference material specifically associated with another resource.
-
E.
places
Indicates that one entity assigns, positions, or puts another entity into a specific location, role, or context.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 29, 2026, 8:11 p.m.