Triple
T1712271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTI Bylaws |
E37208
|
entity |
| Predicate | setOut |
P32233
|
FINISHED |
| Object | powers of the PTI Board |
—
|
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: powers of the PTI Board | Statement: [PTI Bylaws, setOut, powers of the PTI Board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setOut Context triple: [PTI Bylaws, setOut, powers of the PTI Board]
-
A.
setsOut
Indicates that an entity begins a journey, course of action, or process, moving from an initial state or location toward a goal or destination.
-
B.
setsMaximum
Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
-
C.
setInEvent
Indicates that an entity is situated within, occurs during, or is contextually located in a particular event.
-
D.
compositeOutputStandard
Indicates that the entity conforms to or is produced according to a specified composite output standard that defines how multiple outputs are structured or combined.
-
E.
outflow
Indicates the movement or discharge of something from an origin or source to the outside or to another location.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab752034348190a1cc20955ed24f6f |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:30 p.m.