Triple
T35119199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Small Council |
E1014120
|
entity |
| Predicate | membershipControlledBy |
P97456
|
FINISHED |
| Object | king |
—
|
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: king | Statement: [Small Council, membershipControlledBy, king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipControlledBy Context triple: [Small Council, membershipControlledBy, king]
-
A.
memberOwned
Indicates that an entity is owned collectively by its members rather than by external owners or shareholders.
-
B.
membershipRecordedBy
Indicates that the recording or documentation of a membership was carried out or created by a specific agent or system.
-
C.
isUnderControlOf
chosen
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
D.
lifetimeControlledBy
Indicates that the existence or duration of one entity is dependent on and ends with the controlling entity’s lifetime.
-
E.
membershipIndicatedBy
Indicates that an entity’s membership in a group, set, or organization is evidenced, signaled, or made known by another entity or attribute.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:01 p.m.