Triple
T22374648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jade template engine |
E553122
|
entity |
| Predicate | reasonForRename |
P2136
|
FINISHED |
| Object | trademark issue with the name Jade |
—
|
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: trademark issue with the name Jade | Statement: [Jade template engine, reasonForRename, trademark issue with the name Jade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRename Context triple: [Jade template engine, reasonForRename, trademark issue with the name Jade]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
C.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
D.
reasonForAlias
Indicates the justification or underlying cause for which an entity uses or is assigned a particular alias.
-
E.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15806b534819083716c2b090ede42 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.