Triple
T23303178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lvovna |
E590360
|
entity |
| Predicate | addressPattern |
P31500
|
FINISHED |
| Object | first name plus patronymic |
—
|
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: first name plus patronymic | Statement: [Lvovna, addressPattern, first name plus patronymic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressPattern Context triple: [Lvovna, addressPattern, first name plus patronymic]
-
A.
locationPattern
Indicates a recurring or structured spatial relationship, where an entity consistently appears or is arranged in a particular type of location or spatial configuration.
-
B.
addressFormat
chosen
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
C.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
-
D.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
E.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19724de488190ac8eb89253c8dd53 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:04 p.m.