Triple
T29391188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USART |
E745371
|
entity |
| Predicate | dataFramedAs |
P166724
|
FINISHED |
| Object | start bit |
—
|
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: start bit | Statement: [USART, dataFramedAs, start bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataFramedAs Context triple: [USART, dataFramedAs, start bit]
-
A.
dataFile
Indicates a relationship where one entity serves as or is associated with a specific data file used, stored, or referenced by another entity.
-
B.
dataAvailableAs
Indicates that specific data can be accessed or obtained in a particular form, format, or representation.
-
C.
framesAs
Indicates how one entity presents, characterizes, or interprets another entity or situation in a particular light or context.
-
D.
data
Indicates that one entity serves as informational content, measurements, or recorded values associated with another entity.
-
E.
frame
Indicates placing or presenting something within a particular context, structure, or perspective that shapes how it is interpreted.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669ff3b2081909ecfc701841c6532 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:42 p.m.