Triple
T25679699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naranjo |
E643903
|
entity |
| Predicate | hasArchaeologicalGroup |
P166590
|
FINISHED |
| Object | Central Acropolis |
—
|
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: Central Acropolis | Statement: [Naranjo, hasArchaeologicalGroup, Central Acropolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalGroup Context triple: [Naranjo, hasArchaeologicalGroup, Central Acropolis]
-
A.
hasArchaeologicalExcavationsBy
Indicates that archaeological excavations at a site or location are or were conducted by a specified person, group, or organization.
-
B.
hasArchaeologicalProject
Indicates that an entity is associated with or involved in a specific archaeological project.
-
C.
hasArchaeologicalResearch
Indicates that archaeological research has been conducted on, or is associated with, a given entity.
-
D.
hasArchaeologicalCulture
Indicates that an entity is associated with, belongs to, or is characterized by a particular archaeological culture.
-
E.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 21, 2026, 7:45 p.m.