Triple
T26014547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Infiernito |
E646988
|
entity |
| Predicate | monolithFunction |
P138151
|
FINISHED |
| Object | gnomon |
—
|
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: gnomon | Statement: [El Infiernito, monolithFunction, gnomon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monolithFunction Context triple: [El Infiernito, monolithFunction, gnomon]
-
A.
metaFunction
Indicates that one function operates on, describes, or manipulates other functions or their behavior at a higher (meta) level.
-
B.
epicFunction
Indicates that an entity serves a grand, highly significant, or climactic role or purpose within a larger context or process.
-
C.
capsuleFunction
Indicates that a capsule is designed or used to perform a particular function, role, or therapeutic purpose.
-
D.
conceptualFunction
Indicates a relationship where one entity serves as an abstract or conceptual function that operates on, transforms, or maps another entity within a conceptual or theoretical framework.
-
E.
structureFunction
chosen
Indicates that one entity’s physical or organizational structure serves a particular function or role in relation to another 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605b7eb6881909e1768f5f856be32 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:03 a.m.