Triple
T10086835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Rapid Deployable Corps Greece |
E215242
|
entity |
| Predicate | staffComposition |
P12729
|
FINISHED |
| Object | multinational staff |
—
|
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: multinational staff | Statement: [NATO Rapid Deployable Corps Greece, staffComposition, multinational staff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: staffComposition Context triple: [NATO Rapid Deployable Corps Greece, staffComposition, multinational staff]
-
A.
personnelComposition
chosen
Indicates the makeup or distribution of people or roles within a group, organization, or unit.
-
B.
partyComposition
Indicates how the members or elements of a group or party are arranged, distributed, or combined to form that party as a whole.
-
C.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
D.
teamComponent
Indicates that one entity functions as a component, member, or sub-unit within a larger team or group entity.
-
E.
creativeTeamMember
Indicates that an entity participates as a member of a team responsible for creative work or production.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04745b48190a77c422eb76b6660 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.