Triple
T17520550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OneHotEncoder |
E426668
|
entity |
| Predicate | isAppliedBefore |
P113783
|
FINISHED |
| Object | model training |
—
|
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: model training | Statement: [OneHotEncoder, isAppliedBefore, model training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAppliedBefore Context triple: [OneHotEncoder, isAppliedBefore, model training]
-
A.
appliedBefore
chosen
Indicates that one action, process, or condition was applied earlier in time than another.
-
B.
firstAppliedTo
Indicates that an action, process, or treatment was initially used on or directed toward a particular entity before any others.
-
C.
fullyAppliedTo
Indicates that an action, function, or process has been completely and exhaustively applied to a target entity, with no remaining parameters or partial application.
-
D.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
E.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d23cf08190925510344fa36f57 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.