Triple
T33433686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TextEncoderStream |
E856193
|
entity |
| Predicate | encodingNameFixed |
P177407
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [TextEncoderStream, encodingNameFixed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingNameFixed Context triple: [TextEncoderStream, encodingNameFixed, true]
-
A.
zoneNameEncoding
Indicates how the name of a zone is represented or encoded in a specific format or scheme.
-
B.
fixationOnName
Indicates an intense or persistent focus, attention, or obsession directed specifically toward a particular name.
-
C.
encodingPrefix
Indicates that one encoding scheme or representation serves as the initial or leading segment of another encoding.
-
D.
conversionName
Indicates that one entity is the name or label assigned to a specific conversion event or conversion process associated with another entity.
-
E.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:36 a.m.