Triple
T31716375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Getaway Special program |
E809466
|
entity |
| Predicate | allowedParticipants |
P180241
|
FINISHED |
| Object | universities |
—
|
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: universities | Statement: [NASA Getaway Special program, allowedParticipants, universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedParticipants Context triple: [NASA Getaway Special program, allowedParticipants, universities]
-
A.
allowsParticipationIn
chosen
Indicates that one entity grants another entity the right or permission to take part in a specific activity, event, or process.
-
B.
welcomesParticipantsOf
Indicates that one entity receives or greets the participants associated with another entity in a friendly or accepting manner.
-
C.
allowsNILParticipants
Indicates that the relationship or action permits the involvement of participants that may be unspecified, missing, or null (NIL).
-
D.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
E.
participantWith
Indicates that an entity takes part in an event, activity, or process together with another specified entity.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 30, 2026, 11:17 p.m.