Triple
T30667344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Society expedition to observe the transit of Venus |
E780697
|
entity |
| Predicate | captainOfVessel |
P884
|
FINISHED |
| Object | James Cook |
—
|
NE NERFINISHED |
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: James Cook | Statement: [Royal Society expedition to observe the transit of Venus, captainOfVessel, James Cook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainOfVessel Context triple: [Royal Society expedition to observe the transit of Venus, captainOfVessel, James Cook]
-
A.
captain
chosen
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
B.
captainInName
Indicates that an entity’s name or title explicitly includes the word “Captain.”
-
C.
namedVesselOf
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
-
D.
shipName
Indicates the name assigned to a specific ship in the relationship.
-
E.
captainAtTimeOfSinking
Indicates that the subject was serving as the ship’s captain at the specific time when the ship sank.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68ae52e2c81909f0addf854790be2 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:31 p.m.