Triple
T5468841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aigai |
E122779
|
entity |
| Predicate | majorDiscoveries |
P45249
|
FINISHED |
| Object | royal tombs with rich grave goods |
—
|
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: royal tombs with rich grave goods | Statement: [Aigai, majorDiscoveries, royal tombs with rich grave goods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorDiscoveries Context triple: [Aigai, majorDiscoveries, royal tombs with rich grave goods]
-
A.
discoveriesInclude
chosen
Indicates that one entity’s set of discoveries contains or encompasses the other entity as a discovered item.
-
B.
majorExplorationIn
Indicates that an entity’s primary field of exploration, investigation, or study is within a specified domain or area.
-
C.
eraOfScience
Indicates that one entity is a historical period characterized by particular developments or features in science associated with the other entity.
-
D.
co-discoveredWith
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
E.
notableScientist
Indicates that the subject is a scientist who is widely recognized for significant contributions or impact in their field.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.