Triple
T33388220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobá archaeological site |
E854976
|
entity |
| Predicate | discoveredByScholars |
P182434
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Cobá archaeological site, discoveredByScholars, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredByScholars Context triple: [Cobá archaeological site, discoveredByScholars, early 20th century]
-
A.
discoveredByScholarsYear
chosen
Indicates the year in which scholars discovered, identified, or formally recognized the subject.
-
B.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
-
C.
discoveredBy
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
D.
causeOfDiscovery
Indicates that one entity is the reason or factor that led to the discovery of another entity.
-
E.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:35 a.m.