Triple
T21203968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagoda ship model |
E522528
|
entity |
| Predicate | representsActivity |
P110358
|
FINISHED |
| Object | commercial whaling |
—
|
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: commercial whaling | Statement: [Lagoda ship model, representsActivity, commercial whaling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsActivity Context triple: [Lagoda ship model, representsActivity, commercial whaling]
-
A.
portraysActivity
chosen
Indicates that one entity visually or narratively represents another entity engaged in a particular activity.
-
B.
coordinatesActivitiesOf
Indicates that one entity organizes, aligns, or manages the activities of another entity or group of entities so they work together effectively.
-
C.
areRepresentedAt
Indicates that one entity serves as a representative or delegate for another entity at a specific place, event, or context.
-
D.
representsInEvent
Indicates that an entity serves as a representative or proxy for another entity within the context of a specific event.
-
E.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7343367308190b1b772d3c8e25dcb |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:19 p.m.