Triple
T2657298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resource Management Offices |
E54642
|
entity |
| Predicate | typeOfCoordination |
P19448
|
FINISHED |
| Object | budget formulation |
—
|
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: budget formulation | Statement: [Resource Management Offices, typeOfCoordination, budget formulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCoordination Context triple: [Resource Management Offices, typeOfCoordination, budget formulation]
-
A.
cooperationType
chosen
Indicates the specific kind or form of cooperative relationship that exists between the related entities.
-
B.
coordinationBody
Indicates that an entity serves as an organizing or governing body that coordinates the activities, policies, or interactions of other entities.
-
C.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
D.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
E.
hasCoordinatesType
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94c61a08190bdf5e1caeff3e788 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.