Triple
T34821967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Eu |
E1003803
|
entity |
| Predicate | linkedRoleOfHolder |
P93157
|
FINISHED |
| Object | heir to the Brazilian throne |
—
|
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: heir to the Brazilian throne | Statement: [Countess of Eu, linkedRoleOfHolder, heir to the Brazilian throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRoleOfHolder Context triple: [Countess of Eu, linkedRoleOfHolder, heir to the Brazilian throne]
-
A.
associatedWithTitleHolderRole
chosen
Indicates a relationship where an entity is connected to, or linked with, a role held by a title holder.
-
B.
linkRole
Indicates a role or function that an entity plays within a specific link or relationship between entities.
-
C.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
D.
associatedWithRoleOfIssuer
Indicates that one entity is connected to or involved in the capacity, function, or responsibilities of an issuer.
-
E.
associatedWithRoleOfNameBearer
Indicates that an entity is connected to or involved with the specific role or function held by a designated name bearer.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4 p.m.