Triple
T30422998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian culture |
E773947
|
entity |
| Predicate | roleInSupra |
P165140
|
FINISHED |
| Object | tamada |
—
|
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: tamada | Statement: [Georgian culture, roleInSupra, tamada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSupra Context triple: [Georgian culture, roleInSupra, tamada]
-
A.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
-
B.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
-
C.
roleInMatter
Indicates that an entity holds a specific role or capacity in relation to a particular matter, case, or issue.
-
D.
roleOn
chosen
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
E.
basisRole
Indicates that one role serves as the foundational or underlying role upon which another role or function is defined or derived.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: April 29, 2026, 8:06 p.m.