Triple
T26813412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aho–Corasick algorithm |
E672058
|
entity |
| Predicate | isExactMatching |
P85206
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aho–Corasick algorithm, isExactMatching, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExactMatching Context triple: [Aho–Corasick algorithm, isExactMatching, true]
-
A.
supportsExactMatch
chosen
Indicates that one entity fully upholds or is compatible with another entity only when there is an exact, unaltered match between them.
-
B.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
C.
includesMatchType
Indicates that one entity’s set or collection contains an element with a specified type of match (e.g., exact, partial, or pattern-based) to another entity.
-
D.
sameMatchAs
Indicates that two entities are considered equivalent or represent the same underlying match or correspondence in a given context.
-
E.
isExactSince
Indicates that a condition, state, or relationship has held precisely from a specific starting time onward, with that start time being exact rather than approximate.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a83c8ec8190ba1f49371889e547 |
completed | May 2, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:30 a.m.