Triple
T35305230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الناصرة |
E1019617
|
entity |
| Predicate | تاريخياً |
P43343
|
FINISHED |
| Object | مدينة عربية فلسطينية |
—
|
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: مدينة عربية فلسطينية | Statement: [الناصرة, تاريخياً, مدينة عربية فلسطينية]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: تاريخياً Context triple: [الناصرة, تاريخياً, مدينة عربية فلسطينية]
-
A.
historical
chosen
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
B.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
C.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
D.
نقش_تاریخی
Indicates that an entity has played a historical role or has had a significant impact within a particular historical context or period.
-
E.
historicallyEncompassed
Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904ec4dc8190bebc92e83e5a0a95 |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.