Triple
T28514814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TechGirls |
E721584
|
entity |
| Predicate | typeOfExchange |
P80605
|
FINISHED |
| Object | international cultural exchange |
—
|
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: international cultural exchange | Statement: [TechGirls, typeOfExchange, international cultural exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfExchange Context triple: [TechGirls, typeOfExchange, international cultural exchange]
-
A.
isExchangedVia
Indicates that something is transferred or traded from one party to another through a specified medium, channel, or mechanism.
-
B.
typeOfTrading
Indicates a relationship where one entity specifies the kind or category of trading activity associated with another entity.
-
C.
exchangeType
chosen
Indicates the kind or category of exchange occurring between entities, such as the method, direction, or nature of what is being traded or transferred.
-
D.
baseExchange
Indicates an exchange relationship where one entity serves as the base or reference for converting, trading, or swapping value with another.
-
E.
exchangeSymbolType
Indicates the type or category of symbol used to represent an asset on a particular 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: April 28, 2026, 3:16 a.m.