Triple
T18537956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zawyet el-Aryan |
E453014
|
entity |
| Predicate | hasResearchIssue |
P132058
|
FINISHED |
| Object | limited modern archaeological access |
—
|
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: limited modern archaeological access | Statement: [Zawyet el-Aryan, hasResearchIssue, limited modern archaeological access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchIssue Context triple: [Zawyet el-Aryan, hasResearchIssue, limited modern archaeological access]
-
A.
hasResearchStatus
Indicates that an entity holds a particular stage or condition within a research process, such as planned, in progress, completed, or published.
-
B.
hasResearchFinding
Indicates that an entity has produced, contains, or is associated with a specific research finding or result.
-
C.
hasResearched
Indicates that an entity has conducted study, investigation, or systematic inquiry into another entity or topic.
-
D.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
E.
hasResearchGoal
Indicates that an entity has a specific research objective, aim, or target it is pursuing or designed to address.
- F. None of above. chosen
Provenance (4 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534030bd88190b25b95305a12a0c1 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.