Triple
T192572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MoEDAL |
E3751
|
entity |
| Predicate | searchesFor |
P2773
|
FINISHED |
| Object | magnetic monopoles |
—
|
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: magnetic monopoles | Statement: [MoEDAL, searchesFor, magnetic monopoles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchesFor Context triple: [MoEDAL, searchesFor, magnetic monopoles]
-
A.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
B.
searchesRegion
Indicates that an entity performs a search operation within, or targeting, a specified geographic or administrative region.
-
C.
searchesSignalType
chosen
Indicates that an entity actively looks for or queries a specific type or category of signal.
-
D.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
E.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a259669ba08190a5be1d2e10e70b27 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a2567567508190b3a41329a15c7156 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.