Triple
T18112062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marinship shipyards |
E433502
|
entity |
| Predicate | workforceIncluded |
P36154
|
FINISHED |
| Object | women |
—
|
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: women | Statement: [Marinship shipyards, workforceIncluded, women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workforceIncluded Context triple: [Marinship shipyards, workforceIncluded, women]
-
A.
associatedWithWorkforce
chosen
Indicates a relationship in which an entity is connected or related to a particular workforce, such as its members, activities, or management.
-
B.
hasWorkforceType
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
C.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
D.
employersInclude
Indicates that a specified set or group of employers contains, as members, the employer or employers referenced by the other argument.
-
E.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd3422c81908396a21bd53f3e47 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.