Triple
T5839086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of cassation |
E129546
|
entity |
| Predicate | sometimesAlsoActsAs |
P13125
|
FINISHED |
| Object | supreme court in civil and criminal matters |
—
|
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: supreme court in civil and criminal matters | Statement: [court of cassation, sometimesAlsoActsAs, supreme court in civil and criminal matters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesAlsoActsAs Context triple: [court of cassation, sometimesAlsoActsAs, supreme court in civil and criminal matters]
-
A.
alsoServesAs
chosen
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
B.
isAlsoUsedAs
Indicates that something serves an additional function or role beyond its primary one.
-
C.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
-
D.
alsoServedAs
Indicates that an entity held an additional role or position beyond the primary one already mentioned.
-
E.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.