Triple
T29605752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Document Consumer |
E754571
|
entity |
| Predicate | performsTransaction |
P192292
|
FINISHED |
| Object | ITI-18 Registry Stored Query |
—
|
NE NERFINISHED |
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: ITI-18 Registry Stored Query | Statement: [Document Consumer, performsTransaction, ITI-18 Registry Stored Query]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsTransaction Context triple: [Document Consumer, performsTransaction, ITI-18 Registry Stored Query]
-
A.
performsOperation
Indicates that one entity carries out or executes a specific operation on or for another entity.
-
B.
performsAction
Indicates that an entity carries out, executes, or engages in a specified action or activity.
-
C.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
D.
performsFrom
Indicates that an action, performance, or operation is carried out starting from a particular source, origin, or initial context.
-
E.
performsWork
Indicates that one entity carries out, executes, or engages in work or tasks for or on behalf of another entity or context.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 28, 2026, 6:25 p.m.