Triple
T17791346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tel Qeiyafa |
E444167
|
entity |
| Predicate | inscriptionsLanguageHypotheses |
P89667
|
FINISHED |
| Object | early Hebrew |
—
|
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: early Hebrew | Statement: [Tel Qeiyafa, inscriptionsLanguageHypotheses, early Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionsLanguageHypotheses Context triple: [Tel Qeiyafa, inscriptionsLanguageHypotheses, early Hebrew]
-
A.
inscriptionsLanguage
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
B.
secondaryLanguageOfInscriptions
Indicates that a specified language serves as the secondary language used in the inscriptions associated with a given entity.
-
C.
officialLanguageOfInscriptions
Indicates the language officially used in the inscriptions associated with a particular entity.
-
D.
languageHypothesis
chosen
Indicates a proposed or inferred relationship concerning the language used, such as a conjecture about which language applies or how language is involved in a given context.
-
E.
hasLanguageOfArchaeologicalInterpretation
Indicates that an entity uses or is associated with a particular language in which archaeological findings or data are interpreted or described.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48797408081908c48d98e1525ae87 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.