Triple
T28594445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperanto Wikipedia |
E723735
|
entity |
| Predicate | hasWatchlistFunction |
P60284
|
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: [Esperanto Wikipedia, hasWatchlistFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWatchlistFunction Context triple: [Esperanto Wikipedia, hasWatchlistFunction, yes]
-
A.
typeOfWatchlist
Indicates the specific category or classification of a given watchlist within a broader monitoring or tracking system.
-
B.
supportsPageWatchlist
chosen
Indicates that an entity provides functionality for users to watch or track changes to a specific page via a watchlist.
-
C.
requiresAccountToWatch
Indicates that accessing or viewing the content is only possible if the user has an account.
-
D.
hasWaitingList
Indicates that there exists a queue or list of entities waiting for access to, or participation in, the referenced resource, service, or opportunity.
-
E.
hasLookout
Indicates that one entity serves as a lookout or watchful observer for another entity, monitoring for potential events, threats, or changes.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 4:21 a.m.