Triple
T25300249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krabi-Krabong |
E634324
|
entity |
| Predicate | sharesPrinciplesWith |
P66652
|
FINISHED |
| Object | Muay Thai |
—
|
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: Muay Thai | Statement: [Krabi-Krabong, sharesPrinciplesWith, Muay Thai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPrinciplesWith Context triple: [Krabi-Krabong, sharesPrinciplesWith, Muay Thai]
-
A.
sharesPrinciple
chosen
Indicates that two or more entities are based on, guided by, or adhere to the same underlying principle or fundamental rule.
-
B.
sharesPracticesWith
Indicates that two entities engage in or follow similar methods, behaviors, or operational practices.
-
C.
sharesValuesWith
Indicates that two entities hold similar or compatible beliefs, principles, or priorities.
-
D.
providesPrinciplesFor
Indicates that one entity supplies the foundational rules, guidelines, or theoretical basis that another entity follows or is built upon.
-
E.
collectivePrinciple
Indicates a relationship where a rule, norm, or guiding idea is shared, upheld, or applied by a group as a whole rather than by individuals independently.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 21, 2026, 1:24 p.m.