Triple
T23884267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linda Schele |
E600285
|
entity |
| Predicate | significantPlaceOfActivity |
P36296
|
FINISHED |
| Object | Palenque |
—
|
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: Palenque | Statement: [Linda Schele, significantPlaceOfActivity, Palenque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantPlaceOfActivity Context triple: [Linda Schele, significantPlaceOfActivity, Palenque]
-
A.
possiblePlaceOfActivity
Indicates that a location is a plausible or candidate site where the referenced entity may carry out or have carried out an activity.
-
B.
significantEventPlace
Indicates the place where a significant event occurred or is associated with an entity.
-
C.
significantPlaceType
Indicates the type or category of place that holds particular significance in relation to the subject.
-
D.
eventLocationOfNotableActivity
chosen
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
E.
notableLocationUse
Indicates that a location is notably used for a particular purpose, activity, or function associated with the subject.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ccfbbe4c819093e590709719ab72 |
completed | April 29, 2026, 9:18 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:24 p.m.