Triple
T33027506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TYPE |
E845080
|
entity |
| Predicate | parameterERepresentation |
P176382
|
FINISHED |
| Object | EBCDIC |
—
|
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: EBCDIC | Statement: [TYPE, parameterERepresentation, EBCDIC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameterERepresentation Context triple: [TYPE, parameterERepresentation, EBCDIC]
-
A.
parameterIRepresentation
Indicates that an entity serves as a representation or encoding of a specific parameter used by another entity or process.
-
B.
parameterARepresentation
Indicates that one entity serves as a representation, encoding, or stand-in for the parameter or argument role labeled "A" in relation to another entity or process.
-
C.
componentRepresents
Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
-
D.
representationType
Indicates the specific form or mode in which something is represented or expressed (e.g., as a symbol, image, model, or description).
-
E.
effectOnRepresentation
Indicates how one entity influences, alters, or determines the form, quality, or characteristics of another entity’s representation.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:23 a.m.