Triple
T5922323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Should.js |
E131727
|
entity |
| Predicate | exampleAssertion |
P52973
|
FINISHED |
| Object | (1).should.be.exactly(1) |
—
|
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: (1).should.be.exactly(1) | Statement: [Should.js, exampleAssertion, (1).should.be.exactly(1)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleAssertion Context triple: [Should.js, exampleAssertion, (1).should.be.exactly(1)]
-
A.
supportsAssertionLibraries
Indicates that one entity provides compatibility with or functionality for using specific assertion libraries in conjunction with another entity.
-
B.
assertsNonexistenceOf
Indicates that one entity explicitly claims or states that another entity does not exist.
-
C.
assertedControlBy
Indicates that one entity has taken or claimed authoritative power or dominance over another entity, typically through deliberate action or declaration.
-
D.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
-
E.
equalityCondition
chosen
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.