Triple
T29055441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urartian mythology |
E735371
|
entity |
| Predicate | hasRoyalPatron |
P62899
|
FINISHED |
| Object | Menua |
—
|
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: Menua | Statement: [Urartian mythology, hasRoyalPatron, Menua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalPatron Context triple: [Urartian mythology, hasRoyalPatron, Menua]
-
A.
hasRoyalPatronageSince
Indicates that an entity has been under the official support or sponsorship of a royal person or institution starting from a specified point in time.
-
B.
grantedRoyalPatronageBy
Indicates that an individual, group, or institution has officially received support, endorsement, or sponsorship from a member of a royal family.
-
C.
patronessOfCountry
Indicates that a female patron (often a saint or protective figure) serves as the spiritual or symbolic guardian of a specific country.
-
D.
patronRuler
Indicates a relationship where one entity serves as a protective or sponsoring ruler or sovereign authority over another.
-
E.
patronMonarch
chosen
Indicates a relationship where a monarch acts as a patron, providing support, sponsorship, or protection to another party.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 10:11 a.m.