Triple
T29900102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradox Engine |
E759385
|
entity |
| Predicate | isLegalIn |
P155172
|
FINISHED |
| Object | Vintage |
—
|
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: Vintage | Statement: [Paradox Engine, isLegalIn, Vintage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegalIn Context triple: [Paradox Engine, isLegalIn, Vintage]
-
A.
legalExceptionUnitedStates
Indicates that the usual legal rule or requirement does not apply in the United States due to a specific statutory, regulatory, or judicially recognized exception.
-
B.
legalIn
chosen
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
-
C.
legality
Indicates that an action, object, or situation conforms to, violates, or is evaluated in terms of formal laws or legal rules.
-
D.
legalLicenseJurisdiction
Indicates the legal authority or geographic area under whose laws a particular license is granted, valid, or enforced.
-
E.
legalCodeAppliesTo
Indicates that a particular legal code or statute is applicable to, or governs, a specified subject, situation, or entity.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6772e14d48190a9c4dda3d35d0f37 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:06 p.m.