Triple
T30355336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speaker's Table |
E772126
|
entity |
| Predicate | universeOrganizationType |
P60680
|
FINISHED |
| Object | secret ruling council |
—
|
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: secret ruling council | Statement: [Speaker's Table, universeOrganizationType, secret ruling council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeOrganizationType Context triple: [Speaker's Table, universeOrganizationType, secret ruling council]
-
A.
organizationType
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
B.
inUniverseOrganization
chosen
Indicates that an organization exists and operates within a specified fictional or narrative universe.
-
C.
creatorOrganizationType
Indicates the type or category of organization that created or is responsible for the entity.
-
D.
foundedOrganizationType
Indicates that an entity established or created an organization of a specified type (e.g., company, nonprofit, institution).
-
E.
responsibleOrganizationType
Indicates the type or category of organization that holds responsibility for a given action, resource, or obligation.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 7:56 p.m.