Triple
T12630172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Majesty |
E301617
|
entity |
| Predicate | governsPronoun |
P106108
|
FINISHED |
| Object | third person singular |
—
|
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: third person singular | Statement: [Majesty, governsPronoun, third person singular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsPronoun Context triple: [Majesty, governsPronoun, third person singular]
-
A.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
B.
governsRoleOf
Indicates that one entity has authority or control over the role, responsibilities, or functions assigned to another entity.
-
C.
governsGender
Indicates that one entity determines or constrains the gender classification or gender-related properties of another entity.
-
D.
governingForm
Indicates that one entity specifies or embodies the authoritative rules, structure, or format that control or regulate another entity.
-
E.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
- F. None of above. chosen
Provenance (4 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:15 p.m.