Triple
T16812857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head of the Housatonic |
E408657
|
entity |
| Predicate | timingEquipment |
P21771
|
FINISHED |
| Object | electronic timing system |
—
|
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: electronic timing system | Statement: [Head of the Housatonic, timingEquipment, electronic timing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timingEquipment Context triple: [Head of the Housatonic, timingEquipment, electronic timing system]
-
A.
timingStandard
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
B.
timingPartner
Indicates that one entity serves as a temporal counterpart or reference point for another, aligning their actions or events in time.
-
C.
timingMethod
chosen
Indicates the method or technique used to measure or record the timing of an event or process.
-
D.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
E.
timingParameter
Indicates a relationship where one entity specifies or controls a temporal setting, constraint, or configuration parameter that determines the timing behavior of another entity or process.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2df5c888190a462614e1432c357 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.