Triple
T35359438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrović-Njegoš |
E1021431
|
entity |
| Predicate | modernHeadOfHouseClaim |
P137788
|
FINISHED |
| Object | Mihailo Petrović-Njegoš |
—
|
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: Mihailo Petrović-Njegoš | Statement: [Petrović-Njegoš, modernHeadOfHouseClaim, Mihailo Petrović-Njegoš]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernHeadOfHouseClaim Context triple: [Petrović-Njegoš, modernHeadOfHouseClaim, Mihailo Petrović-Njegoš]
-
A.
modernClaimant
chosen
Indicates that an entity is a present-day or contemporary holder or asserter of a particular title, right, or claim.
-
B.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
C.
reignClaim
Indicates a claim or assertion by an entity that it has the right to rule or hold sovereign authority over a domain or people.
-
D.
dynasticClaim
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
-
E.
houseClaim
Indicates a relationship where an entity asserts ownership, rights, or entitlement to a particular house or housing property.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:03 p.m.