Triple
T2526813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LA (NSW) |
E56052
|
entity |
| Predicate | appliesToInstitutionType |
P29027
|
FINISHED |
| Object | legislative body |
—
|
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: legislative body | Statement: [LA (NSW), appliesToInstitutionType, legislative body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToInstitutionType Context triple: [LA (NSW), appliesToInstitutionType, legislative body]
-
A.
eligibleInstitution
Indicates that an institution satisfies specified criteria or requirements to qualify for a particular program, benefit, or status.
-
B.
impliesForInstitution
Indicates that one condition, rule, or statement logically leads to or necessitates another specifically within the context of an institution.
-
C.
usedByInstitutionType
Indicates that something (such as a resource, tool, or service) is utilized or employed by a particular type or category of institution.
-
D.
recognizedAsInstitutionBy
Indicates that an entity is acknowledged or accepted as an institution by a specified recognizing party.
-
E.
associatedInstitutionType
chosen
Indicates the type or category of institution with which an entity is associated.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd255f0d081908d20cfb812c4bfc1 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.