Triple
T27589581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenStack Placement |
E699761
|
entity |
| Predicate | laterSeparatedAs |
P130866
|
FINISHED |
| Object | independent service |
—
|
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: independent service | Statement: [OpenStack Placement, laterSeparatedAs, independent service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSeparatedAs Context triple: [OpenStack Placement, laterSeparatedAs, independent service]
-
A.
laterSeparatedFrom
chosen
Indicates that one entity became separated from another at a later time than some referenced separation event.
-
B.
separatedUntil
Indicates that two entities remain apart or not in contact up to a specified time or condition.
-
C.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
D.
separatedAlongWith
Indicates that an entity becomes separated from something while simultaneously being accompanied or grouped with another specified entity during the separation.
-
E.
wouldHaveBeenSeparatedFrom
Indicates a hypothetical or counterfactual situation in which one entity would have been divided, detached, or kept apart from another entity if certain conditions had occurred.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 27, 2026, 2:05 p.m.