Triple
T16171733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MultiFinder |
E392454
|
entity |
| Predicate | replacedBehavior |
P121988
|
FINISHED |
| Object | single-tasking Finder |
—
|
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: single-tasking Finder | Statement: [MultiFinder, replacedBehavior, single-tasking Finder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedBehavior Context triple: [MultiFinder, replacedBehavior, single-tasking Finder]
-
A.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
B.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
C.
replacedInterface
Indicates that one interface has been substituted or superseded by another interface.
-
D.
replacedClass
Indicates that one class has been superseded or substituted by another class, typically in a versioning or refactoring context.
-
E.
replacedStandard
Indicates that one standard has been superseded or taken the place of another standard.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb7ab1481908fc35bfc8c56e5f2 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.