Triple
T17720144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arsenalna |
E442311
|
entity |
| Predicate | formerSovietStation |
P128716
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Arsenalna, formerSovietStation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSovietStation Context triple: [Arsenalna, formerSovietStation, yes]
-
A.
attachedToSpaceStation
Indicates that an object is physically connected or secured to a space station.
-
B.
spaceStationType
Indicates the specific functional or structural category to which a space station belongs (e.g., research, military, commercial).
-
C.
spaceStationName
Indicates that an entity has the specified name of a space station.
-
D.
establishedResearchStation
Indicates that an entity founded or set up a research station at a particular location or for a particular purpose.
-
E.
spaceStationServed
Indicates that a particular space station is or was serviced, supplied, or supported by a specific mission, vehicle, or service entity.
- F. None of above. chosen
Provenance (4 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4748520a881908dc3446d33236ff7 |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d018227c8190b6624a2199e765e8 |
completed | April 18, 2026, 6:40 p.m. |
Created at: April 10, 2026, 10:07 a.m.