Triple
T21802533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIH PDU |
E538271
|
entity |
| Predicate | exchangedBetween |
P107265
|
FINISHED |
| Object | intermediate systems |
—
|
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: intermediate systems | Statement: [IIH PDU, exchangedBetween, intermediate systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangedBetween Context triple: [IIH PDU, exchangedBetween, intermediate systems]
-
A.
exchanged
chosen
Indicates a reciprocal transfer of something (such as information, goods, or services) between two or more entities.
-
B.
exchangedFor
Indicates that one entity has been traded or substituted in return for another entity.
-
C.
facilitatedExchangeOf
Indicates that one entity made it easier or more efficient for another entity to carry out an exchange or transfer between parties.
-
D.
exchangeType
Indicates the kind or category of exchange occurring between entities, such as the method, direction, or nature of what is being traded or transferred.
-
E.
cooperatedInExchangeFor
Indicates that one entity collaborated or assisted another specifically in return for some form of compensation, benefit, or agreed-upon exchange.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.