Triple
T29108345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connectionist Temporal Classification |
E736823
|
entity |
| Predicate | lossFamily |
P43002
|
FINISHED |
| Object | negative log-likelihood loss |
—
|
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: negative log-likelihood loss | Statement: [Connectionist Temporal Classification, lossFamily, negative log-likelihood loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lossFamily Context triple: [Connectionist Temporal Classification, lossFamily, negative log-likelihood loss]
-
A.
lossType
chosen
Indicates the specific category or nature of a loss associated with an entity or event.
-
B.
fareFamily
Indicates a relationship that classifies a fare or ticket into a specific fare family or category within a pricing structure.
-
C.
focusFamily
Indicates that one entity directs primary attention, concern, or priority toward their family or familial relationships.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
familia
Indicates a familial relationship or bond between entities, such as being members of the same family.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661bc4db08190bd91745a1ebfc2ae |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:17 a.m.