Triple
T27146860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نتسيرت عيليت |
E681973
|
entity |
| Predicate | تسمية_أخرى |
P39
|
FINISHED |
| Object | نتسيرت عيليت (العبرية: נצרת עילית) |
—
|
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: نتسيرت عيليت (العبرية: נצרת עילית) | Statement: [نتسيرت عيليت, تسمية_أخرى, نتسيرت عيليت (العبرية: נצרת עילית)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: تسمية_أخرى Context triple: [نتسيرت عيليت, تسمية_أخرى, نتسيرت عيليت (العبرية: נצרת עילית)]
-
A.
alternativeNameMeaning
Indicates that one entity expresses the meaning or interpretation of an alternative name used for another entity.
-
B.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
C.
alsoKnownAs
chosen
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
D.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
E.
otherCommonName
Indicates that an entity is known by an additional, alternative common name besides its primary one.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f624c6dff08190ba0573eba9d63449 |
completed | May 2, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:12 a.m.