Triple
T28390338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GV |
E719136
|
entity |
| Predicate | refersToInstitutionSector |
P121996
|
FINISHED |
| Object | public |
—
|
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: public | Statement: [GV, refersToInstitutionSector, public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToInstitutionSector Context triple: [GV, refersToInstitutionSector, public]
-
A.
hasInstitutionalSector
chosen
Indicates that an entity is associated with, classified under, or belongs to a particular institutional sector within an economic, organizational, or regulatory framework.
-
B.
servesInstitution
Indicates that one entity provides services or functions in support of a particular institution.
-
C.
centralInstitutionOf
Indicates that one institution serves as the primary or main institutional center for another entity, such as an organization, system, or region.
-
D.
involvesInstitution
Indicates that an action, event, or relationship includes or is associated with an institution as a participating party.
-
E.
servesInstitutionalArea
Indicates that an entity provides services or functions in support of a specific institutional area or domain.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 1:13 a.m.