Triple
T13106642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAS Program |
E310858
|
entity |
| Predicate | allowsOrderingMethod |
P88387
|
FINISHED |
| Object | direct ordering by authorized agencies |
—
|
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: direct ordering by authorized agencies | Statement: [MAS Program, allowsOrderingMethod, direct ordering by authorized agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsOrderingMethod Context triple: [MAS Program, allowsOrderingMethod, direct ordering by authorized agencies]
-
A.
hasOrderingMethod
chosen
Indicates that there is a specific method or procedure used to place or arrange an order for something.
-
B.
supportsOrderAttribute
Indicates that one entity is capable of handling, recognizing, or providing a specified attribute associated with an order.
-
C.
canOrder
Indicates that one entity has the ability or permission to place an order for another entity or item.
-
D.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
E.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98154c9f48190aeca779d97151759 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.