Triple
T30773765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prospekt Lenina |
E783601
|
entity |
| Predicate | hasMultipleInstancesIn |
P62241
|
FINISHED |
| Object | Russian 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: Russian cities | Statement: [Prospekt Lenina, hasMultipleInstancesIn, Russian cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleInstancesIn Context triple: [Prospekt Lenina, hasMultipleInstancesIn, Russian cities]
-
A.
hasMultiplePhysicalInstances
Indicates that a single conceptual entity is realized or exists as more than one distinct physical instance.
-
B.
hasMultiple
chosen
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
C.
hasMultipleCreations
Indicates that an entity is associated with more than one distinct creation or produced work.
-
D.
numberOfInstances
Indicates the quantity or count of distinct occurrences or instances associated with a given entity or context.
-
E.
hasMultipleHoldersSimultaneously
Indicates that a given item, role, or resource is concurrently possessed, controlled, or occupied by more than one holder at the same 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 29, 2026, 8:40 p.m.