Triple
T37167777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | constitutional court |
E920834
|
entity |
| Predicate | mayBeSeparateFrom |
P186453
|
FINISHED |
| Object | supreme court |
—
|
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: supreme court | Statement: [constitutional court, mayBeSeparateFrom, supreme court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeSeparateFrom Context triple: [constitutional court, mayBeSeparateFrom, supreme court]
-
A.
canBeHeldSeparatelyFrom
chosen
Indicates that one entity is capable of being physically or conceptually separated and held apart from another entity.
-
B.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
-
C.
separatedAlongWith
Indicates that an entity becomes separated from something while simultaneously being accompanied or grouped with another specified entity during the separation.
-
D.
wouldHaveBeenSeparatedFrom
Indicates a hypothetical or counterfactual situation in which one entity would have been divided, detached, or kept apart from another entity if certain conditions had occurred.
-
E.
canBeSplitAmong
Indicates that something is divisible into parts that can be distributed among multiple recipients or groups.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.