Triple
T23857690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Label 2 |
E592354
|
entity |
| Predicate | freeRelease |
P154212
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [No Label 2, freeRelease, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freeRelease Context triple: [No Label 2, freeRelease, true]
-
A.
freeFrom
Indicates that one entity does not contain, is not affected by, or is exempt from another specified entity, condition, or constraint.
-
B.
releaseFrom
Indicates that one entity causes or authorizes another entity to be freed, discharged, or removed from a prior state of confinement, obligation, or restriction.
-
C.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
D.
releaseObtainedBy
Indicates that a particular release results from, or is produced through, a specified obtaining or acquisition process.
-
E.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
- F. None of above. chosen
Provenance (4 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98bf1d081908279fc145371afa5 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:12 p.m.