Triple
T33645687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smolensk fortress |
E861953
|
entity |
| Predicate | numberOfGatesOriginal |
P21387
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Smolensk fortress, numberOfGatesOriginal, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfGatesOriginal Context triple: [Smolensk fortress, numberOfGatesOriginal, 9]
-
A.
numberOfGates
chosen
Indicates the quantity of gates associated with or belonging to an entity.
-
B.
lengthOfEachGate
Indicates the measurement of the individual length associated with each gate in a set or system.
-
C.
numberOfGatehouses
Indicates the quantity of gatehouses associated with or present at a given entity or location.
-
D.
hasBoardingGatesFor
Indicates that a location or facility provides designated boarding gates used for embarking passengers onto specific transportation services (such as flights or trains).
-
E.
hasPassengerBoardingGates
Indicates that an entity is associated with or contains one or more passenger boarding gates used for embarking or disembarking passengers.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0340784c488190aa6c7c9be2e8a434 |
completed | May 12, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_6a033f33eddc819091507716f6ed7d7d |
completed | May 12, 2026, 2:54 p.m. |
Created at: May 1, 2026, 1:42 a.m.