Triple
T38643753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Island Expeditions |
E938665
|
entity |
| Predicate | supportsRoleComposition |
P10591
|
FINISHED |
| Object | flexible roles |
—
|
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: flexible roles | Statement: [Island Expeditions, supportsRoleComposition, flexible roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRoleComposition Context triple: [Island Expeditions, supportsRoleComposition, flexible roles]
-
A.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
B.
supportsRoleSwap
chosen
Indicates that one entity enables or allows the interchange of roles or responsibilities with another entity.
-
C.
supportsMembersOf
Indicates that one entity provides assistance, backing, or advocacy specifically to the members of another entity or group.
-
D.
usesRoleTypes
Indicates that an entity employs or is associated with specific role classifications or role types within a given context.
-
E.
includesRoles
Indicates that one entity contains or encompasses one or more specified roles within its scope or structure.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.