Triple
T13728858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khirbet Qana |
E329736
|
entity |
| Predicate | typeOfDebate |
P57644
|
FINISHED |
| Object | biblical toponymy identification debate |
—
|
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: biblical toponymy identification debate | Statement: [Khirbet Qana, typeOfDebate, biblical toponymy identification debate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDebate Context triple: [Khirbet Qana, typeOfDebate, biblical toponymy identification debate]
-
A.
fieldOfDebate
chosen
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
-
B.
debateTopic
Indicates that one entity serves as the subject or issue being discussed or argued about in a debate involving another entity.
-
C.
partOfDebate
Indicates that one entity is a component, segment, or participant within a larger debate or argumentative exchange.
-
D.
majorDebateWith
Indicates a significant, often public or formal, debate or dispute occurring between two entities.
-
E.
mainDebateTopic
Indicates that a specified subject or issue is the primary focus or central topic of a particular debate or discussion.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f746cc8190abde237bbb7e6c78 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.