Triple
T18004557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Second Division |
E430711
|
entity |
| Predicate | typicalNumberOfZones |
P57453
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Russian Second Division, typicalNumberOfZones, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNumberOfZones Context triple: [Russian Second Division, typicalNumberOfZones, 5]
-
A.
numberOfZones
chosen
Indicates the quantity of distinct zones associated with or contained by a given entity.
-
B.
numberOfThemedZones
Indicates the total count of distinct themed zones associated with or contained within an entity.
-
C.
zoneNumberRange
Indicates that there is an associated range of zone numbers, typically specifying the minimum and maximum zone identifiers applicable in a given context.
-
D.
numberOfBays
Indicates the count of distinct bays associated with or contained within a given entity.
-
E.
hasDRSZones
Indicates that one entity possesses, defines, or is associated with specific DRS (Disaster Recovery Site or similarly defined) zones.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b3eb1f748190904c8894d22cf85f |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.