Triple
T8300404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia unified login |
E194335
|
entity |
| Predicate | storesAccountsIn |
P63988
|
FINISHED |
| Object | central authentication database |
—
|
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: central authentication database | Statement: [Wikimedia unified login, storesAccountsIn, central authentication database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesAccountsIn Context triple: [Wikimedia unified login, storesAccountsIn, central authentication database]
-
A.
storesIndexesIn
Indicates that one entity maintains and holds index data within another storage entity or system.
-
B.
store
chosen
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
C.
storesConfigurationFor
Indicates that one entity holds or maintains configuration settings that are used by or apply to another entity.
-
D.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
E.
storesMetadataIn
Indicates that one entity holds or maintains descriptive or configuration metadata about another entity within a specified storage location or system.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e879c588190a6f95cf7795541ad |
completed | March 31, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.