Triple
T20618655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Superhits! |
E506638
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Maria |
—
|
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: Maria | Statement: [International Superhits!, hasPart, Maria]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maria Context triple: [International Superhits!, hasPart, Maria]
-
A.
Maria
Maria is a feminine given name of Hebrew origin, widely used across many cultures and languages.
-
B.
Maria
chosen
Maria is a track on Rage Against the Machine’s 2000 album "The Battle of Los Angeles," known for its politically charged lyrics and aggressive rap metal sound.
-
C.
Maria
Maria is a coastal municipality on Siquijor Island in the Philippines known for its rural communities and scenic seaside landscapes.
-
D.
Maria
Maria Vladimirovna Dolgorukova was a Russian noblewoman from the prominent Dolgorukov family, known historically as the first wife of Tsar Michael I of Russia.
-
E.
Maria
Maria is the given name of Grand Duchess Maria Alexandrovna of Russia, a 19th-century Russian imperial princess who became Duchess of Edinburgh through marriage into the British royal family.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abdf9d7c8190969247a4ae55b781 |
completed | April 20, 2026, 10:42 p.m. |
Created at: April 16, 2026, 11:41 a.m.