Triple
T30843624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larcum Kendall |
E785576
|
entity |
| Predicate | K1UsedOn |
P2367
|
FINISHED |
| Object | James Cook’s second voyage |
—
|
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: James Cook’s second voyage | Statement: [Larcum Kendall, K1UsedOn, James Cook’s second voyage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: K1UsedOn Context triple: [Larcum Kendall, K1UsedOn, James Cook’s second voyage]
-
A.
usedOn
chosen
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
B.
eraUsedIn
Indicates that something (such as a method, standard, or practice) was in active use during a specified historical or temporal era.
-
C.
kitType
Indicates the specific category or configuration of a kit associated with an entity or activity.
-
D.
engineUsedIn
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
-
E.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69145041c81909275df4e885f090a |
completed | May 3, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:46 p.m.