Triple
T32498439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JWS |
E830587
|
entity |
| Predicate | mechanismOf |
P84491
|
FINISHED |
| Object | JWT |
—
|
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: JWT | Statement: [JWS, mechanismOf, JWT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanismOf Context triple: [JWS, mechanismOf, JWT]
-
A.
mechanismBy
Indicates that one entity occurs, is produced, or is brought about by means of another entity, which serves as its mechanism or causal process.
-
B.
mechanismExample
Indicates that one entity serves as an illustrative example of the mechanism or process by which another entity operates or produces an effect.
-
C.
mentionsMechanism
Indicates that one entity explicitly refers to or describes the mechanism, process, or causal pathway by which another entity operates or produces an effect.
-
D.
relatedMechanism
chosen
Indicates a causal or functional connection where one entity serves as the mechanism or process through which another entity’s effect, behavior, or outcome is brought about.
-
E.
definesMechanism
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c441b8c88190ade9e43a3cd77f3f |
completed | May 3, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:59 a.m.