Triple
T25259058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTT-40 |
E633252
|
entity |
| Predicate | trainingStage |
P36516
|
FINISHED |
| Object | Stage-I 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: Stage-I training | Statement: [HTT-40, trainingStage, Stage-I training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingStage Context triple: [HTT-40, trainingStage, Stage-I training]
-
A.
trainingStatus
chosen
Indicates the current state or phase of an entity within a training or learning process.
-
B.
pretrainingStage
Indicates that an entity is in, or associated with, an early training phase prior to its main or final training stage.
-
C.
trainingVersion
Indicates that one entity is a specific training iteration, release, or configuration derived from or associated with another entity.
-
D.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
E.
trainingStability
Indicates the degree to which a training process proceeds consistently without large fluctuations, divergence, or instability in its behavior or outcomes.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:13 p.m.