Triple
T17485822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PsycARTICLES |
E425774
|
entity |
| Predicate | hasSearchFunctionality |
P21822
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [PsycARTICLES, hasSearchFunctionality, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSearchFunctionality Context triple: [PsycARTICLES, hasSearchFunctionality, yes]
-
A.
hasSearchField
Indicates that an entity includes or is associated with a search input field that can be used to query or filter information.
-
B.
searchFeature
chosen
Indicates that an entity provides or supports functionality for searching or querying information or items.
-
C.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
D.
isSearchable
Indicates that the referenced entity can be discovered or retrieved through a search operation or query.
-
E.
hasCreativeSearch
Indicates a relationship where an entity employs or is associated with a search process or functionality that involves creativity, innovation, or generative exploration beyond standard search methods.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d1f4708190b7c4d61326a2c4a4 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.