Triple
T18213201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Prognostic Index |
E436083
|
entity |
| Predicate | stageCriterion |
P130262
|
FINISHED |
| Object | Ann Arbor stage III or IV |
—
|
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: Ann Arbor stage III or IV | Statement: [International Prognostic Index, stageCriterion, Ann Arbor stage III or IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageCriterion Context triple: [International Prognostic Index, stageCriterion, Ann Arbor stage III or IV]
-
A.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
B.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
C.
stageElement
Indicates that one entity functions as a component or part within the structure or configuration of another entity.
-
D.
stageReached
Indicates that a process, task, or entity has arrived at or completed a specific stage or phase within a defined progression.
-
E.
stageAfter
Indicates that one stage occurs later in sequence or order than another specified stage.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e22a26308190a6720b41a9bbfc2d |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:32 a.m.