Triple
T35060397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | تل مجيدو |
E1011575
|
entity |
| Predicate | يضم بقايا |
P16216
|
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.
remnantsInclude
Indicates that the remaining parts or leftovers of one entity contain or consist of another entity.
-
B.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
C.
hasRemainsOf
chosen
Indicates that one entity physically contains, preserves, or is associated with the leftover physical traces or remnants of another entity.
-
D.
containedPartOf
Indicates that one entity is physically or logically included within and forms a part of another entity.
-
E.
describesRemnant
Indicates that one entity provides a description or characterization of another entity that is a remaining part, leftover, or surviving trace of something previously whole or present.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7860a1154819088c0faac06bc3852 |
completed | May 3, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.