Triple
T3546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Association of American Universities |
E66
|
entity |
| Predicate | hasActivity |
P81
|
FINISHED |
| Object | advocacy for federal research funding |
—
|
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: advocacy for federal research funding | Statement: [Association of American Universities, hasActivity, advocacy for federal research funding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivity Context triple: [Association of American Universities, hasActivity, advocacy for federal research funding]
-
A.
activity
chosen
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
B.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
C.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
-
D.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
E.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23bcc8eb48190b897cc331563980a |
completed | Feb. 28, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_69a23994309081909ff3e869deef2156 |
completed | Feb. 28, 2026, 12:40 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.