Triple
T25980600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Boudeuse (ship) |
E646058
|
entity |
| Predicate | carriedRole |
P45565
|
FINISHED |
| Object | cartographers |
—
|
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: cartographers | Statement: [La Boudeuse (ship), carriedRole, cartographers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedRole Context triple: [La Boudeuse (ship), carriedRole, cartographers]
-
A.
carriedOutRole
Indicates that an entity performed or fulfilled a specific role in the context of an activity, event, or process.
-
B.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
C.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
D.
hasCargoRole
chosen
Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
-
E.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 8:54 a.m.