Triple
T31840479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PG 779 |
E812788
|
entity |
| Predicate | hasExcavationNumber |
P183521
|
FINISHED |
| Object | PG 779 |
—
|
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: PG 779 | Statement: [PG 779, hasExcavationNumber, PG 779]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExcavationNumber Context triple: [PG 779, hasExcavationNumber, PG 779]
-
A.
excavatedFor
Indicates that something has been dug out or uncovered from the ground specifically for the benefit, use, or purpose of another entity.
-
B.
excavatedTo
Indicates that one entity has been dug out, uncovered, or removed from the ground or another material and transferred or exposed to another specified location or state.
-
C.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
D.
excavatedAs
Indicates that one entity has been dug out, uncovered, or removed from its surrounding material or context in the form or role of another specified entity.
-
E.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: April 30, 2026, 11:49 p.m.