Triple
T23254584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon class sailing |
E581829
|
entity |
| Predicate | crewRole2 |
P21967
|
FINISHED |
| Object | middle crew |
—
|
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: middle crew | Statement: [Dragon class sailing, crewRole2, middle crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewRole2 Context triple: [Dragon class sailing, crewRole2, middle crew]
-
A.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
B.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
crewDescription
Indicates a descriptive statement that characterizes or summarizes the composition, roles, or attributes of a crew involved in an entity or event.
-
E.
hasCrewRole
chosen
Indicates that an entity serves in a specific role or position within a crew associated with 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193fadac881908579b5729718ee41 |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:11 p.m.