Triple
T1095745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q-balls |
E24266
|
entity |
| Predicate | searchesVia |
P23048
|
FINISHED |
| Object | astrophysical constraints |
—
|
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: astrophysical constraints | Statement: [Q-balls, searchesVia, astrophysical constraints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchesVia Context triple: [Q-balls, searchesVia, astrophysical constraints]
-
A.
searchFeature
Indicates that an entity provides or supports functionality for searching or querying information or items.
-
B.
searchesRegion
Indicates that an entity performs a search operation within, or targeting, a specified geographic or administrative region.
-
C.
seekerType
Indicates the specific category or role of the entity that is performing or initiating the seeking action in the relationship.
-
D.
soughtTitle
Indicates that an entity actively pursued or attempted to obtain a particular title or position.
-
E.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99e92308190b8a8c499e1630672 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:42 p.m.