Triple
T17483301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRZ-L |
E425716
|
entity |
| Predicate | dcComponent |
P14071
|
FINISHED |
| Object | non-zero for unbalanced data |
—
|
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: non-zero for unbalanced data | Statement: [NRZ-L, dcComponent, non-zero for unbalanced data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dcComponent Context triple: [NRZ-L, dcComponent, non-zero for unbalanced data]
-
A.
componentCC
Indicates that one entity is a component or constituent part of another entity within a coordinated or composite construction.
-
B.
component1
chosen
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
C.
componentElement
Indicates that one entity is a constituent or part of another, larger entity or structure.
-
D.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
-
E.
componentAct
Indicates that an action or behavior is performed by a component as part of a larger system or process.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d06c2881909632845dd7a6b1e3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.