Triple
T24696001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mastaba G 7210–7220 |
E611585
|
entity |
| Predicate | excavationSiteCode |
P48233
|
FINISHED |
| Object | G 7210–7220 |
—
|
NE NERFINISHED |
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: G 7210–7220 | Statement: [Mastaba G 7210–7220, excavationSiteCode, G 7210–7220]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavationSiteCode Context triple: [Mastaba G 7210–7220, excavationSiteCode, G 7210–7220]
-
A.
archaeologicalSiteCode
chosen
Indicates that a specific standardized code is assigned to identify and reference an archaeological site.
-
B.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
-
C.
hasArchaeologicalSiteCode
Indicates that an entity is associated with a specific archaeological site identified by a formal site code.
-
D.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
E.
excavationInstitution
Indicates the institution or organization responsible for conducting or overseeing an excavation.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:21 a.m.