Triple
T30843638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larcum Kendall |
E785576
|
entity |
| Predicate | chronometerK1Cost |
P191097
|
FINISHED |
| Object | very expensive to produce |
—
|
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: very expensive to produce | Statement: [Larcum Kendall, chronometerK1Cost, very expensive to produce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronometerK1Cost Context triple: [Larcum Kendall, chronometerK1Cost, very expensive to produce]
-
A.
chronometerNumber
Indicates that an entity has been assigned a specific chronometer identification number, linking it to that unique timekeeping device record.
-
B.
clockManufacturer
Indicates that one entity is the producer or maker of a clock associated with another entity.
-
C.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
D.
hasClockMechanismDate
Indicates that an entity has an associated date specifying when its clock mechanism was created, installed, or became effective.
-
E.
clockMechanism
Indicates that one entity functions as the internal mechanism or movement that drives the operation of a clock.
- F. None of above. chosen
Provenance (4 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: April 29, 2026, 8:46 p.m.