Triple
T22805823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Simon |
E564528
|
entity |
| Predicate | nationalityTraditionally |
P34270
|
FINISHED |
| Object | Jewish |
—
|
LITERAL FINISHED |
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: Jewish | Statement: [Saint Simon, nationalityTraditionally, Jewish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalityTraditionally Context triple: [Saint Simon, nationalityTraditionally, Jewish]
-
A.
hasNationalityTraditionally
chosen
Indicates that an entity is traditionally or historically associated with a particular nationality, regardless of current legal or formal citizenship status.
-
B.
countryOfNamingTradition
Indicates the country whose cultural or linguistic naming conventions are used to form or interpret a given name.
-
C.
nationalityInText
Indicates that a person's nationality is mentioned or specified within a given text.
-
D.
isTraditionallyIdentifiedAs
Indicates that one entity is customarily or historically recognized or labeled as being the same as, or corresponding to, another entity.
-
E.
nationalityAdjectiveOf
Indicates that one term is the adjectival form derived from the nationality associated with the other term.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5c193481908550993e2547515d |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.