Triple
T12784353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabot |
E305584
|
entity |
| Predicate | revealedDuring |
P47249
|
FINISHED |
| Object | festal processions |
—
|
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: festal processions | Statement: [Tabot, revealedDuring, festal processions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealedDuring Context triple: [Tabot, revealedDuring, festal processions]
-
A.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
-
B.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
-
C.
isRevealedTo
Indicates that previously hidden or unknown information becomes known to a specific entity or group.
-
D.
exposedDuring
chosen
Indicates that something becomes visible, accessible, or subject to influence specifically within a given time period, event, or contextual interval.
-
E.
isRevealedIn
Indicates that something becomes known, disclosed, or made apparent within a particular context, medium, or situation.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5cb3c08190b8e1e22de8b96e17 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.