Triple
T7332073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Three |
E169025
|
entity |
| Predicate | memberInstitutionControl |
P26524
|
FINISHED |
| Object | private |
—
|
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: private | Statement: [Little Three, memberInstitutionControl, private]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberInstitutionControl Context triple: [Little Three, memberInstitutionControl, private]
-
A.
hasInstitutionalControl
Indicates that one entity exercises formal authority, governance, or decision-making power over an institution or organizational body.
-
B.
institutionalControl
Indicates that one institution has governing, regulatory, or managerial authority over another entity or activity.
-
C.
focusesOnInstitutionControl
Indicates that the primary emphasis or concern is on controlling or governing institutions and their decision-making processes.
-
D.
memberInstitutionCharacteristic
chosen
Indicates that a specific characteristic or attribute is associated with a member institution within a larger organization or system.
-
E.
grantedByInstitution
Indicates that something (such as a status, permission, or resource) is conferred or authorized by an institution.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:03 p.m.