Triple
T36100398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eloise Taylor |
E1044187
|
entity |
| Predicate | monarchSubjectOf |
P184677
|
FINISHED |
| Object | Charles III |
—
|
NE NERFINISHED |
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: Charles III | Statement: [Eloise Taylor, monarchSubjectOf, Charles III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchSubjectOf Context triple: [Eloise Taylor, monarchSubjectOf, Charles III]
-
A.
monarchAssociatedWith
Indicates a relationship where a monarch has a notable connection or affiliation with another entity, such as a person, place, institution, or event.
-
B.
monarchIs
Indicates that one entity serves as the ruling monarch (such as king, queen, or equivalent sovereign) of another entity, typically a state or territory.
-
C.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
D.
monarchRepresentedBy
Indicates that a monarch is formally represented or acted on behalf of by another person or entity in official or ceremonial capacities.
-
E.
monarchName
Indicates the personal name or official regnal name of a monarch in the relationship.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b3e0f1c88190985feab6cee8b05e |
completed | May 3, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:08 p.m.