Triple
T24645811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Stuart |
E610106
|
entity |
| Predicate | hasWorkedOnArchaeologicalSite |
P33849
|
FINISHED |
| Object | Tikal |
—
|
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: Tikal | Statement: [David Stuart, hasWorkedOnArchaeologicalSite, Tikal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkedOnArchaeologicalSite Context triple: [David Stuart, hasWorkedOnArchaeologicalSite, Tikal]
-
A.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
B.
hasArchaeologicalProject
Indicates that an entity is associated with or involved in a specific archaeological project.
-
C.
hasArchaeologicalExcavationsBy
chosen
Indicates that archaeological excavations at a site or location are or were conducted by a specified person, group, or organization.
-
D.
hasArchaeologicalResearch
Indicates that archaeological research has been conducted on, or is associated with, a given entity.
-
E.
hasArchaeologicalSiteStatus
Indicates that an entity holds an officially recognized status or designation as an archaeological site.
- 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_69e2c4d350a481909170482bc2ce6af9 |
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, 2:33 a.m.