Triple
T2279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRE Transactions |
E41
|
entity |
| Predicate | medium |
P166
|
FINISHED |
| Object |
—
|
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: print | Statement: [IRE Transactions, medium, print]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: medium Context triple: [IRE Transactions, medium, print]
-
A.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
B.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
C.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
influenced
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
- 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_69a22cde80848190b62c5f556b4d62ba |
completed | Feb. 27, 2026, 11:46 p.m. |
| NER | Named-entity recognition | batch_69a2316d88a08190b2e03041674b5674 |
completed | Feb. 28, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69a230c3ee4481908216244c38aa8aef |
completed | Feb. 28, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69a2316cbe58819096cc036d6e3b103c |
completed | Feb. 28, 2026, 12:06 a.m. |
Created at: Feb. 27, 2026, 11:48 p.m.