Triple
T5689799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | space brigade |
E125399
|
entity |
| Predicate | canBeComposedOf |
P39652
|
FINISHED |
| Object | multiple space battalions |
—
|
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: multiple space battalions | Statement: [space brigade, canBeComposedOf, multiple space battalions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeComposedOf Context triple: [space brigade, canBeComposedOf, multiple space battalions]
-
A.
canBeConstructedWith
Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
-
B.
composedFor
Indicates that a creative work (typically a piece of music) was specifically written or created for a particular person, group, event, or purpose.
-
C.
composedIn
Indicates that a creative work was written or musically composed within a particular place or during a specific time period.
-
D.
definesComposition
chosen
Indicates that one entity specifies or establishes the structural or component makeup of another entity.
-
E.
previouslyComposedOf
Indicates that something was formerly made up of or constituted by certain parts, elements, or members, but no longer is.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.