Triple
T32709097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JavaMail |
E836349
|
entity |
| Predicate | relicensedAs |
P41932
|
FINISHED |
| Object | EPL |
—
|
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: EPL | Statement: [JavaMail, relicensedAs, EPL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relicensedAs Context triple: [JavaMail, relicensedAs, EPL]
-
A.
canBeRelicensedUnder
chosen
Indicates that an existing license for something may legally be changed to a different license under specified conditions.
-
B.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
C.
previouslyLicensedAs
Indicates that an entity held a license under a different name or status at some earlier time.
-
D.
laterLicense
Indicates that one license chronologically succeeds another, coming into effect at a later time than the referenced license.
-
E.
tookOverLicenseFrom
Indicates that one entity assumed or acquired a license previously held by another 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c87bf9c481908804bd231d60cd30 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:10 a.m.