Triple
T34585326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSA Honorary Fellowships |
E888027
|
entity |
| Predicate | isNonRemunerative |
P94912
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [INSA Honorary Fellowships, isNonRemunerative, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonRemunerative Context triple: [INSA Honorary Fellowships, isNonRemunerative, true]
-
A.
isNonJudicial
Indicates that an action, process, or decision occurs outside of formal judicial proceedings and is not carried out by a court or judge.
-
B.
nonMonetary
Indicates that the relationship or transaction occurs without the exchange or involvement of money or financial compensation.
-
C.
isNonCashAward
chosen
Indicates that an award is given in a form other than cash, such as goods, services, or other non-monetary benefits.
-
D.
hasNoAdditionalRemuneration
Indicates that an entity does not receive any extra payment or compensation beyond the primary agreed remuneration.
-
E.
nonRefundable
Indicates that something, typically a payment or purchase, cannot be returned or reimbursed once completed.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:03 a.m.