Triple
T15790223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPER |
E382844
|
entity |
| Predicate | stageOfProcedure |
P83617
|
FINISHED |
| Object | after international search |
—
|
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: after international search | Statement: [IPER, stageOfProcedure, after international search]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageOfProcedure Context triple: [IPER, stageOfProcedure, after international search]
-
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.
proceduralStatus
chosen
Indicates the current stage, condition, or progress state of a procedure or process.
-
D.
stage4Type
Indicates that one entity is classified as a specific type or subtype within the fourth stage of a defined multi-stage process or system.
-
E.
decisionProcessStage
Indicates the specific phase or step within a broader decision-making process at which an action, evaluation, or outcome occurs.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.