Triple
T3650982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Regent |
E77415
|
entity |
| Predicate | governsOnBehalfOf |
P4131
|
FINISHED |
| Object | reigning monarch |
—
|
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: reigning monarch | Statement: [Prince Regent, governsOnBehalfOf, reigning monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsOnBehalfOf Context triple: [Prince Regent, governsOnBehalfOf, reigning monarch]
-
A.
actsOnBehalfOf
chosen
Indicates that one entity performs actions or makes decisions as a representative or proxy for another entity.
-
B.
governedEntity
Indicates that one entity exercises authority, control, or governance over another entity.
-
C.
governanceActor
Indicates that an entity plays a role in governing, managing, or overseeing another entity, process, or domain.
-
D.
governingPartner
Indicates that one entity serves as the primary ruling or controlling partner in relation to another within a governance or leadership structure.
-
E.
organizationTypeGoverned
Indicates that one entity governs or has authoritative control over a specific type or category of organization.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc39303bc819090725643e53a96d6 |
completed | March 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.