Triple
T31441731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noe |
E802082
|
entity |
| Predicate | hasNameDayInTraditionsRelatedTo |
P59993
|
FINISHED |
| Object | Noah |
—
|
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: Noah | Statement: [Noe, hasNameDayInTraditionsRelatedTo, Noah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayInTraditionsRelatedTo Context triple: [Noe, hasNameDayInTraditionsRelatedTo, Noah]
-
A.
hasNameDayInSomeCountriesFor
Indicates that an entity is celebrated with a name day, in at least some countries, on behalf of or in relation to another specified entity.
-
B.
hasNameDayRelation
chosen
Indicates a relationship where a person’s name is associated with a specific name day or feast day in a calendar.
-
C.
hasNameDayOrReligiousUsage
Indicates that an entity has an associated name day celebration or is used in a religious or liturgical context.
-
D.
hasNameDay
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
-
E.
hasNameDayInformation
Indicates that there exists associated information about a person’s name day, such as the date or related observances.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 30, 2026, 9:06 p.m.