Triple
T27591483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Policy Agent |
E699796
|
entity |
| Predicate | supportsDecisionAPI |
P199632
|
FINISHED |
| Object | REST |
—
|
NE NERFINISHED |
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: REST | Statement: [Open Policy Agent, supportsDecisionAPI, REST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDecisionAPI Context triple: [Open Policy Agent, supportsDecisionAPI, REST]
-
A.
supportsDecisionOf
Indicates that one entity endorses, backs, or agrees with the decision made by another entity.
-
B.
requiresDecision
Indicates that a choice or judgment must be made regarding the associated entities or situation.
-
C.
hasDecisionStatus
Indicates that a decision or choice is associated with a particular status or outcome state.
-
D.
includesDecisionsBy
Indicates that something contains, encompasses, or takes into account decisions made by a specified party or set of parties.
-
E.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
- F. None of above. chosen
Provenance (4 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
| PDg | Predicate description generation | batch_69ff49f7db2c819094d488d13985334c |
completed | May 9, 2026, 2:51 p.m. |
Created at: April 27, 2026, 2:05 p.m.