Triple
T32082792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lead I |
E819343
|
entity |
| Predicate | recordsElectricalActivityBetween |
P193067
|
FINISHED |
| Object | right arm |
—
|
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: right arm | Statement: [Lead I, recordsElectricalActivityBetween, right arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsElectricalActivityBetween Context triple: [Lead I, recordsElectricalActivityBetween, right arm]
-
A.
recordedBetween
Indicates that an event or data item was recorded at a time that falls within a specified start and end time interval.
-
B.
recordsEventsVia
Indicates that one entity captures or logs events through the mechanism, system, or medium provided by another entity.
-
C.
recordEvent
Indicates that an entity logs or stores information about a specific occurrence or action as an event.
-
D.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
E.
dataRecordedAt
Indicates that specific data was captured or stored at a particular time or location.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 1, 2026, 12:24 a.m.