Triple
T14859309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitutional Court of Luxembourg |
E349446
|
entity |
| Predicate | cannotBeSeizedBy |
P61996
|
FINISHED |
| Object | individuals directly |
—
|
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: individuals directly | Statement: [Constitutional Court of Luxembourg, cannotBeSeizedBy, individuals directly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeSeizedBy Context triple: [Constitutional Court of Luxembourg, cannotBeSeizedBy, individuals directly]
-
A.
canBeSeizedBy
Indicates that one entity is legally or physically able to be taken control of, captured, or confiscated by another entity.
-
B.
cannotBeHeldBy
chosen
Indicates that one entity is not allowed or not able to possess, carry, or be in control of another entity.
-
C.
cannotBeRemovedBy
Indicates that one entity is not capable of removing, deleting, or otherwise eliminating another entity.
-
D.
cannotBeLeashed
Indicates that one entity is not allowed or not able to be restrained, controlled, or attached using a leash by another entity.
-
E.
canBeLocked
Indicates that an entity has the capability to be secured or made inaccessible by applying a lock or locking mechanism.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44598e48190b759a05ed2d9ecaf |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.