Triple
T19919200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Brazil |
E478742
|
entity |
| Predicate | holderEntitledTo |
P39434
|
FINISHED |
| Object | membership in the Portuguese royal family |
—
|
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: membership in the Portuguese royal family | Statement: [Prince of Brazil, holderEntitledTo, membership in the Portuguese royal family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderEntitledTo Context triple: [Prince of Brazil, holderEntitledTo, membership in the Portuguese royal family]
-
A.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
B.
holderMustBe
Indicates that a specified entity is required to be the holder or possessor of another entity or resource.
-
C.
holderMayBe
Indicates that a particular entity is allowed or permitted to serve as the holder or possessor of another entity.
-
D.
holderMayUseTitle
Indicates that the holder is permitted to use or bear a specified title.
-
E.
hasRightsOver
chosen
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c3d990819089386d9f30323e8c |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.