Triple
T27637520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jest DOM |
E696506
|
entity |
| Predicate | matcher |
P163311
|
FINISHED |
| Object | .toHaveTextContent |
—
|
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: .toHaveTextContent | Statement: [Jest DOM, matcher, .toHaveTextContent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matcher Context triple: [Jest DOM, matcher, .toHaveTextContent]
-
A.
matchResult
Indicates the outcome or final status produced by a particular match or game between participants.
-
B.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
C.
mayMatch
Indicates a potential or permissible correspondence or pairing between two entities, without guaranteeing that the match actually occurs.
-
D.
matchContext
Indicates that two or more entities are related within the same situational, conversational, or environmental setting that frames or influences their interaction.
-
E.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 2:24 p.m.