Triple
T18123636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMA Interim Meeting |
E433810
|
entity |
| Predicate | policyOutcomeUsedFor |
P98
|
FINISHED |
| Object | advocacy positions |
—
|
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 positions | Statement: [AMA Interim Meeting, policyOutcomeUsedFor, advocacy positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyOutcomeUsedFor Context triple: [AMA Interim Meeting, policyOutcomeUsedFor, advocacy positions]
-
A.
usedPolicy
Indicates that an entity applied or followed a particular policy in carrying out an action or decision.
-
B.
usagePolicy
Indicates the rules or conditions governing how something may be used or accessed.
-
C.
governsOutcome
Indicates that one entity has decisive control or influence over the result or consequence affecting another entity.
-
D.
policyOutput
Indicates that a policy or decision-making process produces or yields a particular outcome, result, or output.
-
E.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddebeae88190ae50e9a258b34dbe |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.