Triple
T25075841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shards of Honor |
E628044
|
entity |
| Predicate | omnibusWith |
P16605
|
FINISHED |
| Object | Barrayar |
—
|
NE NERFINISHED |
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: Barrayar | Statement: [Shards of Honor, omnibusWith, Barrayar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: omnibusWith Context triple: [Shards of Honor, omnibusWith, Barrayar]
-
A.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
B.
includedWith
chosen
Indicates that one entity is provided or packaged together as part of another entity.
-
C.
actedTogetherWith
Indicates that two entities participated in the same performance or production, collaborating or appearing together in an acting context.
-
D.
alsoComposedWith
Indicates that something is created or formed together with one or more additional components, highlighting a joint or complementary composition relationship.
-
E.
commissionedWith
Indicates that one entity was created, produced, or initiated as part of the same commissioning event or request as another entity.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45d1966c08190997f5ff8880a3314 |
completed | May 1, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:21 a.m.