Triple
T33687742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangere |
E863086
|
entity |
| Predicate | famousUsageAddressee |
P92617
|
FINISHED |
| Object | Mary Magdalene |
—
|
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: Mary Magdalene | Statement: [Tangere, famousUsageAddressee, Mary Magdalene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousUsageAddressee Context triple: [Tangere, famousUsageAddressee, Mary Magdalene]
-
A.
famousIndividual
Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
-
B.
famousCallBy
Indicates that one entity is famously referred to or called by a particular name or title by another entity or source.
-
C.
addresseeOf
chosen
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
D.
famousCall
Indicates that one entity makes a phone call to another entity who is widely known or celebrated.
-
E.
famousMember
Indicates that an entity is a well-known or widely recognized member of a particular group, organization, or category.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:43 a.m.