Triple
T17517767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of B-R5RB |
E426608
|
entity |
| Predicate | locationSpace |
P13939
|
FINISHED |
| Object | null security space |
—
|
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: null security space | Statement: [Battle of B-R5RB, locationSpace, null security space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationSpace Context triple: [Battle of B-R5RB, locationSpace, null security space]
-
A.
spacePosition
Indicates the spatial location or coordinates of an entity within a defined space or reference frame.
-
B.
locationOnSpacecraft
Indicates that one entity occupies or is situated at a specific place or position on a spacecraft.
-
C.
locationScope
chosen
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
-
D.
coordinatesSpacecraft
Indicates overseeing and directing the movement and positioning of a spacecraft within its operational space.
-
E.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452615a8481909974e9855ea7a8e4 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.