Triple
T7088645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whispersync |
E165137
|
entity |
| Predicate | dataTypeSynced |
P74461
|
FINISHED |
| Object | reading position |
—
|
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: reading position | Statement: [Whispersync, dataTypeSynced, reading position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTypeSynced Context triple: [Whispersync, dataTypeSynced, reading position]
-
A.
dataSyncedTo
Indicates that a set of data has been successfully synchronized from one system or location to another, reflecting the same state or contents.
-
B.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
C.
dataTypeDisplayed
Indicates that a particular data type is currently being shown or rendered in a given context or interface.
-
D.
attributeType
Indicates that one entity specifies the kind or category of attribute that characterizes another entity.
-
E.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e52d26f08190917e5e13b181bdae |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e24af9ac8190b24eee206ba8be36 |
completed | March 27, 2026, 8:02 p.m. |
Created at: March 27, 2026, 2:41 p.m.