Triple
T35847376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Administrative Court of Thailand |
E1036249
|
entity |
| Predicate | partyToCases |
P15954
|
FINISHED |
| Object | administrative agencies |
—
|
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: administrative agencies | Statement: [Administrative Court of Thailand, partyToCases, administrative agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyToCases Context triple: [Administrative Court of Thailand, partyToCases, administrative agencies]
-
A.
partyToCase
chosen
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
B.
legalParties
Indicates that the related entities are formally recognized participants in a legal relationship, case, contract, or proceeding.
-
C.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
D.
judicialPartner
Indicates a formal partnership or collaborative relationship between entities within a judicial or court-related context.
-
E.
partiesAre
Indicates that certain entities are the participants or sides involved in a particular relationship, agreement, or event.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.