Triple
T10259620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P.C.I.J. Series A, No. 17 |
E240560
|
entity |
| Predicate | hasProceduralStage |
P93124
|
FINISHED |
| Object | merits |
—
|
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: merits | Statement: [P.C.I.J. Series A, No. 17, hasProceduralStage, merits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProceduralStage Context triple: [P.C.I.J. Series A, No. 17, hasProceduralStage, merits]
-
A.
hasProceduralRole
Indicates that an entity participates in a process or procedure by fulfilling a specific functional role within that process.
-
B.
hasProceduralHistory
Indicates that an entity is associated with a record or sequence of procedural events, actions, or steps that have occurred over time.
-
C.
hasProceduralInstrument
Indicates that a procedure or process is carried out using, or with the aid of, a specified instrument or tool.
-
D.
hasStageProduction
Indicates that one entity is realized, adapted, or presented as a stage production (such as a play, musical, or theatrical performance) associated with another entity.
-
E.
hasPrologueSometimes
Indicates that an entity occasionally or in some instances includes a prologue.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d2b4ae548190b4a4c671f86b82d1 |
completed | April 7, 2026, 9:47 a.m. |
Created at: April 6, 2026, 11:32 a.m.