Triple
T30843627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larcum Kendall |
E785576
|
entity |
| Predicate | K1Purpose |
P64674
|
FINISHED |
| Object | testing longitude determination at sea |
—
|
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: testing longitude determination at sea | Statement: [Larcum Kendall, K1Purpose, testing longitude determination at sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: K1Purpose Context triple: [Larcum Kendall, K1Purpose, testing longitude determination at sea]
-
A.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
C.
programmedPurpose
Indicates that an entity has been intentionally designed or configured to fulfill a specific function, goal, or behavior.
-
D.
tagPurpose
Indicates the intended role, function, or use associated with a given tag in a particular context.
-
E.
tacticalPurpose
Indicates the specific tactical objective or intended operational role that an action, asset, or decision is meant to achieve within a broader plan or mission.
- 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.